Your message dated Wed, 15 Feb 2012 14:16:37 +0100
with message-id <[email protected]>
and subject line History and Tab completion do not work at all
has caused the Debian Bug report #304365,
regarding History and Tab completion do not work at all
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
304365: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=304365
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ksh
Version: 93q-1
Severity: normal
If I hit ArrowUp -key in ksh93, it do not bring the last command from
history. If I hit <TAB> or <ESC><ESC> , it do not work as Tab
completion at all.
Here is some quote from KSH FAQ:
http://www.kornshell.com/doc/faq.html
---- Clip here ----
Q5. How do I get the arrow keys to work?
A5. Starting with the 'h' point release, on most keyboards you
do not have to do anything to get the arrow keys to work.
However, if they do not generate standard escape sequences,
then you will have to use a keybinding function to get them
to work.
Q6. Does ksh support file name completion?
A6. Yes, it does. The default key binding is <ESC><ESC>
however, starting with the 'g' point release, <TAB> also works
for completion. Note, the vi users need to set -o viraw
in order to get <TAB> completion to work.
Q7. Does ksh support command completion?
A7. If you perform completion on the first word of a command,
ksh will do completion using aliases, functions, and commands.
Q8. Is completion programmable?
A8. Yes, using the key binding mechanism, you can script the behavior
of any key and therefore cause the current contents of any
line to be replaced by any other line.
---- Clip here ----
You may also need some good examples. You'll find some of them from
dotfiles.com , for example this:
http://www.dotfiles.com/files/5/197_.kshrc
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (990, 'testing'), (99, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.11-1-686
Locale: LANG=fi_FI@euro, LC_CTYPE=fi_FI@euro (charmap=ISO-8859-15)
Versions of packages ksh depends on:
ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an
-- no debconf information
--
Juhapekka "naula" Tolvanen * http colon slash slash iki dot fi slash juhtolv
"Lennän taas. Olen juppihippipunkkari ja vaihdan paikkaa. Lennän taas. Turha
meikäläistä yrittääkään kategoriin laittaa. Hei mä lennän taas. Olen
juppihippipunkkari ja vaihdan paikkaa. Lennän taas." Neljä Ruusua
--- End Message ---
--- Begin Message ---
It turns out that this is intended behaviour:
"If VISUAL or EDITOR are not set to a command whose name contains *gmacs*
or *emacs* or *[Vv][Ii]*, then no editor is enabled and history and tab
completion do not work."
I am now able to reproduce it by starting ksh with an empty environment.
I'll suggest ot upstream that they update their FAQ but otherwise, I
will now close the bug.
Oliver
--- End Message ---
