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. 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.
Also the home/end keys don't work for me using konsole (with any of it's
keyboard settings).
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.
But I do like fish --- keep up the good work!
Diggory
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Fish-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fish-users
