[slime-devel] slime feature proposal: message-of-the-day
hi, i have a new slime feature but i'm debating whethere it's actually useful as part of standard slime or just bloat: we have a new variable swank:*motd-pathname* which, when not NIL, is assumed to name a ChangeLog formated file. When we connect slime to swank this file is read and the entries in the last N days are given to slime to be inserted into the repl before the prompt and after the banner. The idea behind this variable is tha a group of programmers would use it to communicate or remind themselves about development related changes (i'm thinking stuff like changes to default startup procedures, moving databases, api changes, test suite results, etc.). so, would this actually be useful or is it just bloat? (including the ChangeLog parser it's around 80 lines of code). -- -Marco Ring the bells that still can ring. Forget your perfect offering. There is a crack in everything. That's how the light gets in. -Leonard Cohen
Hi, Marco Baringer <mb@bese.it> writes:
hi,
i have a new slime feature but i'm debating whethere it's actually useful as part of standard slime or just bloat:
we have a new variable swank:*motd-pathname* which, when not NIL, is assumed to name a ChangeLog formated file. When we connect slime to swank this file is read and the entries in the last N days are given to slime to be inserted into the repl before the prompt and after the banner.
The idea behind this variable is tha a group of programmers would use it to communicate or remind themselves about development related changes (i'm thinking stuff like changes to default startup procedures, moving databases, api changes, test suite results, etc.).
If you're already there one might think about introducing roles and have different messages displayed. You could declare yourself to be a 'slime-developer which would lead to messages concerning (e.g.) internal changes or you could play the role of a 'slime-user and could be given hints when some important functions change or when new features are introduced. Other roles 'slime-newbie (default) - common usage tips 'slime-ignoramus - no messages at all ... Just thinking here... Regards Stefan -- Stefan Kamphausen --- http://www.skamphausen.de a blessed +42 regexp of confusion (weapon in hand) You hit. The format string crumbles and turns to dust.
Hello! On Fri, 03 Nov 2006 16:27:07 +0100, Stefan Kamphausen wrote:
If you're already there one might think about introducing roles and have different messages displayed. You could declare yourself to be a 'slime-developer which would lead to messages concerning (e.g.) internal changes or you could play the role of a 'slime-user and could be given hints when some important functions change or when new features are introduced.
FWIW, seconded :-) Thx, bye, Gismo / Luca
On the other hand, you don't want to grow this thing into a whole newsgroup system... On Fri, 2006-11-03 at 16:27 +0100, Stefan Kamphausen wrote:
Hi,
Marco Baringer <mb@bese.it> writes:
hi,
i have a new slime feature but i'm debating whethere it's actually useful as part of standard slime or just bloat:
we have a new variable swank:*motd-pathname* which, when not NIL, is assumed to name a ChangeLog formated file. When we connect slime to swank this file is read and the entries in the last N days are given to slime to be inserted into the repl before the prompt and after the banner.
The idea behind this variable is tha a group of programmers would use it to communicate or remind themselves about development related changes (i'm thinking stuff like changes to default startup procedures, moving databases, api changes, test suite results, etc.).
If you're already there one might think about introducing roles and have different messages displayed. You could declare yourself to be a 'slime-developer which would lead to messages concerning (e.g.) internal changes or you could play the role of a 'slime-user and could be given hints when some important functions change or when new features are introduced.
Other roles
'slime-newbie (default) - common usage tips 'slime-ignoramus - no messages at all ...
Just thinking here... Regards Stefan
Hi. It's cool, but why this future should be available only for lisp programmers? I far as I understand, the file referenced by *motd-pathname* should be accessible from the local machine. If so, it may be more flexible to implement ChangeLog parser in emacs lisp and turn it into a separate tool, that may be used by any emacs user, not necessary by lisp developer. Regards, -Anton -----Original Message----- From: slime-devel-bounces@common-lisp.net [mailto:slime-devel-bounces@common-lisp.net]On Behalf Of Marco Baringer Sent: Friday, November 03, 2006 5:14 PM To: slime-devel@common-lisp.net Subject: [slime-devel] slime feature proposal: message-of-the-day hi, i have a new slime feature but i'm debating whethere it's actually useful as part of standard slime or just bloat: we have a new variable swank:*motd-pathname* which, when not NIL, is assumed to name a ChangeLog formated file. When we connect slime to swank this file is read and the entries in the last N days are given to slime to be inserted into the repl before the prompt and after the banner. The idea behind this variable is tha a group of programmers would use it to communicate or remind themselves about development related changes (i'm thinking stuff like changes to default startup procedures, moving databases, api changes, test suite results, etc.). so, would this actually be useful or is it just bloat? (including the ChangeLog parser it's around 80 lines of code). -- -Marco Ring the bells that still can ring. Forget your perfect offering. There is a crack in everything. That's how the light gets in. -Leonard Cohen _______________________________________________ slime-devel site list slime-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/slime-devel
"Anton Vodonosov" <vodonosov@mail.ru> writes:
Hi.
It's cool, but why this future should be available only for lisp programmers?
I far as I understand, the file referenced by *motd-pathname* should be accessible from the local machine. If so, it may be more flexible to implement ChangeLog parser in emacs lisp and turn it into a separate tool, that may be used by any emacs user, not necessary by lisp developer.
but what if emacs is on one machine and the lisp is on another? you want the lisp's motd, not the local one right? though you're right, it'd be a lot easier to do in emacs (especially considering the existence of change-log-mode) -- -Marco Ring the bells that still can ring. Forget your perfect offering. There is a crack in everything. That's how the light gets in. -Leonard Cohen
Marco Baringer <mb@bese.it> writes:
i have a new slime feature but i'm debating whethere it's actually useful as part of standard slime or just bloat:
I think it is bloat. It would be better to spend time on improving the manual. Cheers, -- Matthias Köppe -- http://www.math.uni-magdeburg.de/~mkoeppe
If there is interest in improving the manual, I'd like to help. --Jeff On Sat Nov 04, 2006 at 10:57:27AM +0100, Matthias Koeppe wrote:
Marco Baringer <mb@bese.it> writes:
i have a new slime feature but i'm debating whethere it's actually useful as part of standard slime or just bloat:
I think it is bloat. It would be better to spend time on improving the manual.
Cheers, -- Matthias Köppe -- http://www.math.uni-magdeburg.de/~mkoeppe
_______________________________________________ slime-devel site list slime-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/slime-devel
Jeffrey Cunningham <jeffrey@cunningham.net> writes:
If there is interest in improving the manual, I'd like to help.
awesome! want some pointers? as a start you colud just walk throguh the manual and make sure every slime feature is, at least, mentioned in the manual. don't worry about actually explaining it all (the authors will probably have to help with that) but at least a stub section for everything slime can do wolud be nice... -- -Marco Ring the bells that still can ring. Forget your perfect offering. There is a crack in everything. That's how the light gets in. -Leonard Cohen
participants (7)
-
Anton Vodonosov -
Dan Weinreb -
Jeffrey Cunningham -
Luca Capello -
Marco Baringer -
Matthias Koeppe -
Stefan Kamphausen