[slime-devel] Making SLIME ChangeLogs more useful

Mark Harig idirectscm at aim.com
Fri Jan 29 04:46:19 UTC 2010

-----Original Message-----From: Helmut Eller <heller at common-lisp.net>* Mark Evenson [2010-01-28 10:49+0100] writes:> Is there a convention to specify which specialization of a CL generic > function a comment refers to?  Emacs 23.1 just seems to go to the first > DEFMETHOD it finds.No official one and nothing that would be supported.  I tend to writethings like: (inspect-object (cons)).Helmut---- Beware of using nested parenthesized expressions if you want tomaintain the hypertext capability of Change Log mode.  For example,   * slime.el (inspect-object (cons)): [descriptive text]would lead C-c C-c to attempt to locate the definition of the symbol`cons' in the file slime.el, which is probably not what you want.  Theregular expression that Change Log mode uses to identify a symbol inparentheses locates the symbol in the inner-most set of parentheses,rather than the outer-most set of parentheses.If they want to gain the hypertext- like capability that Change Logmode provides, then writers of ChangeLog entries may want to stick tothe simple rule of providing filenames and parenthesized (optionally,comma-separated lists of) symbols whose definitions have been added,changed, or deleted, followed by colons and descriptions.  Then theburden of providing detail about the change falls to the description.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/slime-devel/attachments/20100128/31e4896b/attachment.html>

More information about the slime-devel mailing list