Hello SLIME users,
I am using SLIME CVS version 2007-09-27 in the package "Ready Lisp" that contain Aquamacs for OSX
The auto completion of this SLIME always add one more SPACE in front of the ending double quote, as shown below
(load "/Users/Myname/Documents/Lisp/Mylispfile.lisp ")
Where should I look up in the SLIME files to correct this problem? (to remove the extra space)
Please point me to the file and functions Thanks a lot!
Regards,
John
* Tsunhin John Wong [2008-03-26 02:01+0100] writes:
Hello SLIME users,
I am using SLIME CVS version 2007-09-27 in the package "Ready Lisp" that contain Aquamacs for OSX
The auto completion of this SLIME always add one more SPACE in front of the ending double quote, as shown below
(load "/Users/Myname/Documents/Lisp/Mylispfile.lisp ")
Where should I look up in the SLIME files to correct this problem? (to remove the extra space)
Please point me to the file and functions Thanks a lot!
The function is probably slime-maybe-complete-as-filename in slime.el.
In general you can find the source file for a command with C-h k <key> or C-h f <function>. This displays the documentation and a clickable link to the source file (at least in Emacs, not sure about Aquamacs). In the case above you could have used C-h k TAB which would probably bring up slime-indent-and-complete-symbol and reading a bit its source you would probably use C-h f slime-complete-symbol and after some iterations you would be at slime-maybe-complete-as-filename.
Helmut.
Helmut Eller wrote:
- Tsunhin John Wong [2008-03-26 02:01+0100] writes:
Hello SLIME users,
I am using SLIME CVS version 2007-09-27 in the package "Ready Lisp" that contain Aquamacs for OSX
The auto completion of this SLIME always add one more SPACE in front of the ending double quote, as shown below
(load "/Users/Myname/Documents/Lisp/Mylispfile.lisp ")
Where should I look up in the SLIME files to correct this problem? (to remove the extra space)
Please point me to the file and functions Thanks a lot!
I remember this bug manifesting itself in SBCL and ABCL, so it wasn't specific to the "Ready Lisp" distribution, but never to the point of correcting it in the source: one morning, after updating CVS it went away. As to when in CVS HEAD datewise might be a little tricky, because of the "contrib split" that happened around that time (whereby a directory called 'contrib' is created under the main SLIME code, and all non-essential code is moved therein causing great havoc and gnashing of teeth, but eventually proved to be well worth it". My advice would be to use the CVS version before the "contrib split", and diff the files to the image used in "Ready Lisp".
-
Helmut Eller -
Mark Evenson -
Tsunhin John Wong