2006/1/28, Diggory Hardy <[EMAIL PROTECTED]>:
> When using the command-line history (pressing up arrow), if the line is
> at all modified, it is assumed as a search for the up/down history keys.
> This is sometimes fine, but pressing left then right (or any other
> sequence resulting in the original line?) should continue
> browsing/searching history as previously.
Probably true. I'll update the code to do this.
> Also, there should always be a
> blank line at the end of the history, so if you have a long line after
> pressing up and editing the line (e.g. left to see the rest of the line)
> you don't have to hold the backspace key for a while to get a blank line.
I disagree. Sometimes when a search fails, you want to clear the
commandline and start typing something else, but other times you want
to keep tyyping on whatever command you where searching for.
If a search failure would result in an empty commandline, you'd have
to retype the whole search string if you want to keep typing. If a
search failiure returns the original string, all you have to do to
clear the whole commandline is press Ctrl-C.
> Also the home/end keys don't work for me using konsole (with any of it's
> keyboard settings).
Those keys works out of the box on the Konsole version on my machine.
I'm afraid Konsole is a rather weird terminal emulator, since the
sequence sent by any given key kan be configured. This makes it
practically impossible to ship any terminal based program that works
well with Konsole. How to fix this on your computer:
Type make key_reader while in the fish source directory. This will
create a keylogger program which you can start by running
./key_reader. Now you can press the home and end keys and see what
sequences they generate and update your inputrc files accordingly.
> I dislike the line horizontal autoscrolling to fit a long line onto a
> single line, since it hides most of the line. This leads me to the
> problem above if I try to read a previous line, but even if that were
> fixed I'd prefer not to have autoscrolling hiding some of the line.
This problem will mostly go away once fish supports multiline editing.
I don't know when that is, though.
>
> But I do like fish --- keep up the good work!
Thanks!
>
> Diggory
>
--
Axel
N�HY隊X���'���u���[�������
ަ�k��!�� �W�~�鮆�zk��C� [EMAIL PROTECTED],���� a{�
��,�H��4�m�����Z�� jY�w��ǥrg
