I just have started playing with CLISP. Running at the shell, I
can use <TAB> for completion e.g
*inspect-brow<TAB>
expands to
*inspect-browser*
I prefer to run CLISP inside of Emacs using
inferior-lisp-mode (the pkg "inf-lisp.el"). Is there any easy
way to still have completion of CL symbols?
[Note: I am not using SLIME.]
--
Prof. Jonathan LF King Mathematics dept, Univ. of Florida
From: Raymond Wiker
Subject: Re: Tab-completion (for CLISP) in inferior-lisp-mode in Emacs; possible?
Date:
Message-ID: <m2zm0bue6l.fsf@RawMBP.local>
·········@math.ufl.edu writes:
> I just have started playing with CLISP. Running at the shell, I
> can use <TAB> for completion e.g
>
> *inspect-brow<TAB>
>
> expands to
>
> *inspect-browser*
>
> I prefer to run CLISP inside of Emacs using
> inferior-lisp-mode (the pkg "inf-lisp.el"). Is there any easy
> way to still have completion of CL symbols?
> [Note: I am not using SLIME.]
C-q Tab, perhaps? This is assuming that the problem is caused
by inferior-lisp-mode binds Tab for its own purposes.
Any particular reasons for not using SLIME?
...
> C-q Tab, perhaps?
Alas, C-q Tab does not work on my machine.
> Any particular reasons for not using SLIME?
I may have to <sigh> ... but I had hoped to stick with the
simpler lisp-interaction-mode, that I more-or-less already
understand. I do not need to run lisp on a remote machine.
(Just to check: Does SLIME provide completion for the
underlying CL that it connects to? If so, for which CL
implementations does that work?)
I think CLISP use the GNU readline package (I don't
recall its exact name). Perhaps inferior-lisp-mode, i.e,
comint-mode, is disabling or replacing GNU readline. Are
there any further suggestions on how I can stay in simpler
setting and still have completion for CLISP?
(I can't be the ONLY person with an inferiority complex... )
--
Prof. Jonathan LF King Mathematics dept, Univ. of Florida
From: Zach Beane
Subject: Re: Tab-completion (for CLISP) in inferior-lisp-mode in Emacs; possible?
Date:
Message-ID: <m31wdm9zar.fsf@unnamed.xach.com>
·········@math.ufl.edu writes:
> (Just to check: Does SLIME provide completion for the
> underlying CL that it connects to?
Yes.
> If so, for which CL implementations does that work?)
All of them.
It also provides a lot of other nice features, like jumping to the
source location of functions, macro-aware indentation, arglist
display as you edit, etc.
Zach
From: Matthias Buelow
Subject: Re: Tab-completion (for CLISP) in inferior-lisp-mode in Emacs; possible?
Date:
Message-ID: <5jlvofF8t3pU1@mid.dfncis.de>
·········@math.ufl.edu wrote:
> I think CLISP use the GNU readline package (I don't
> recall its exact name). Perhaps inferior-lisp-mode, i.e,
> comint-mode, is disabling or replacing GNU readline. Are
> there any further suggestions on how I can stay in simpler
> setting and still have completion for CLISP?
Presumably it calls clisp with clisp -I, which disables tab completion.
This is so that stuff with tabs in it which gets pasted over (manually
or by emacs) into the clisp session doesn't trigger the completion. I
don't know if SLIME does it differently or if it's using inferior-lisp mode.
On Aug 29, 3:27 pm, Matthias Buelow <····@incubus.de> wrote:
> ...
> Presumably it calls clisp with clisp -I, which disables tab completion. ...
Thank you for that; I see that now in the CLISP man page.
Alas, it doesn't seem that the problem is there. In Emacs,
I can run `shell' directly and, in the the resulting
*shell* buffer, type "clisp<RET>".
This indeed runs CLISP, but no combination of
TAB
C-q TAB
C-q C-i
with or without <RET>, generates CL completion in the
subshell. I looked at Emacs's comint-mode and
shell-mode Customization variables, and recognized none
that seem to relate to this. I'm flummoxed.
From: Cesar Rabak
Subject: Re: Tab-completion (for CLISP) in inferior-lisp-mode in Emacs; possible?
Date:
Message-ID: <fb7lls$1jf$1@aioe.org>
·········@math.ufl.edu escreveu:
> On Aug 29, 3:27 pm, Matthias Buelow <····@incubus.de> wrote:
>> ...
>> Presumably it calls clisp with clisp -I, which disables tab completion. ...
>
> Thank you for that; I see that now in the CLISP man page.
>
> Alas, it doesn't seem that the problem is there. In Emacs,
> I can run `shell' directly and, in the the resulting
> *shell* buffer, type "clisp<RET>".
>
> This indeed runs CLISP, but no combination of
>
> TAB
> C-q TAB
> C-q C-i
>
> with or without <RET>, generates CL completion in the
> subshell. I looked at Emacs's comint-mode and
> shell-mode Customization variables, and recognized none
> that seem to relate to this. I'm flummoxed.
>
clisp (at least version 2-41) works diferently when under Emacs shell
buffer than in OS shell.
FWIW the problem proton describes with certain keys in foreign keyboard
disappears in Windows.