On Sun, 14 Oct 2007 17:09:41 +0200 "Axel Liljencrantz" <[EMAIL PROTECTED]> wrote:
Dear Axel, it's my 1st post to the list and let me express my heartfelt "thank you" for providing fish shell! Since quite some time I'm doing simple taks to simplify my desktop setup by using less, as well as more simple and powerful applications. Soon, after moving to xmonad WM, I gave another try to fish and now it's my 'default-shell' and I wrote live-pkgbuild to be able to regularly pull from the repo (using beloved darcs :-) > Case insensitive completion > > The way this works is that if there are no case sensitive completions > that match, case insensitive completions are usedas a fallback. If > there is a case insensitive match, then the current argument is > changed to match the case of the completion. All this happens > automatically. There are situations where this is not ideal, but it > seems to me to be the correct behaviour ~99 % of the time. > Specifically, after using it for a long time, I have yet to have any > realworld problems with it. It works nicely for me... > Multiline editing > > When editing a multiline command, the up and down keys move up and > down in the command. When at the top line, up performs a history > search, and the same with down on the bottom line. This makes keyboard > navigation far easier on long commands. I must confess that before I started with fish, using bash was 'minimalistic', ie. although being comfortable with cli, I really never tried to enter multiline-commands in the shell directly, but yesterday I was fascinated how fish depends on other specific tool (like expr) to do the job, keeping the shell simple and powerful at the same time. Kudos for design! > Long commands > > When editing a very wide command, the prompt will jump to it's own > line, so that you have the entire width of the screen at your disposal > for editing your command. I had to tryout this one as well, and it is very nice. > Key bindings > > Key bindings no longer use the inputrc file format. Instead, they are > done using a simple fish builtiin command. There was never any real > benefit from using the inputrc format, since the functions you could > bind to in fish are different from those in readline. The new system > makes it very easy to change the bindings interactively from the > shell. To bind Control-p to the pwd command, write: > > bind \cp pwd > > To bind Alt-h to change home directory to your home directory, type > > bind \eh cd > > Note how the regular escape sequences already supported by the shell > are reused to provide the same functionality here. That means that if > you learn once how to use fish escape sequences, you can reuse the > same knowledge in other places. Didn't have need for the above, but it sounds cool. > If anybody has the time to perform some extra testing of fish to > report bugs, I'd be grateful. I hope to release the new fish version > within a week or two. So far, I did not encounter any bug although I was confused for some time while my ssh-completion does not work, but the problem was solved upon discovering that Arch package put HashKnownHosts option to 'yes' :-) All the best in further enhancing our beloved (fish) shell ;) Sincerely, Gour ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Fish-users mailing list Fish-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fish-users
