Fellow Sluggers,

For what it is worth I have solved my own problem.  The tab is meant to
be a completion character as in the shell.  It doesn't really seem to
work this way, however, causing a segmentation error in a bash-invoked
CLISP instead.  However, in shell invocations of CLISP "Control-V
Control-I (or <TAB>)" provides the correct indentation, and functions
can be compiled normally.  Under Emacs, you just set the
"indent-tabs-mode" to nil: (setq indent-tabs-mode nil) in the
*inferior-lisp* buffer (the setting is buffer-specific and won't affect,
say, a "C-mode" buffer that you might happen to have in the same
invocation of Emacs (as if that would matter with a 40G hard disk). 
This way you also get the proper indentation for s-exps, etc.  For
pre-existing files, simply mark the whole buffer ("Control-X h" is the
quickest way) and then do an "Escape-X untabify" to get rid of tabs (or
rather to substitute them for the appropriate number of spaces).  Of
course, this can be done with "expand", and for a really huge number of
CLISP files it obviously wouldn't be difficult to write an appropriate
shell script, or a Perl one, or whatever.  I don't have libsigisev
intsalled and maybe this has got something to do with the segmentation
error; if anyone can tell me where to get it, or how to get around the
completion problem (while my CLISP responds fine to "readline"
operations, I didn't specifically install this library either, but it's
obviously there somewhere.  In any case, all suggestions would be
welcome.  Maybe this will help someone else who is installing CLISP; I
still get the feeling I have got a great deal to learn.

Dr Malcolm Johnston



-- 
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug

Reply via email to