I've finally gotten around to taking a first stab at multiline editing. There is a patch in the darcs tree that enables this.
Features: * Single-line editing works as before. There should be no missing features. * When the return key follows directly after a backslash, or when the commands on the commandline are not finished (i.e. missing end command(s)), a new line is created without executing the old one. * You can move between the lines using left/right arrow keys, etc.. The whole command can be edited until it is executed. * The entire multiline command is a single history entry. Issues: * Probably various bugs and terminal specific issues. So far, I've only verified that it works when using screen insige gnome-terminal... Let the bug reports start. * Inefficient repaint. Some clever hacking needed. * The current history file format can't support multiline commands stored as a single entry. Don't know what the proper way to handle this is. Changing the format means changing the filenmae, or we'll get into version clashes with older fishes. Or maybe the history should work on a line-by-line level? * Fish should do block indentation. * Backslashes before the newline seem to confuse the syntax highlighting. Comments are welcome. -- Axel ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Fish-users mailing list Fish-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fish-users
