On 10/30/06, Martin Bähr <[EMAIL PROTECTED]> wrote: > On Mon, Oct 30, 2006 at 04:44:45PM +0100, Axel Liljencrantz wrote: > > Not sure that's a good idea. For example, when you are searching the > > history, if you come across a multiline entry, you will be stuck. > > not really. > you only have to hit the arrow a few more times to get to the next > entry. > the current way is verry annoying, it makes me lose work, because i keep > forgetting that i can not switch lines in multiline mode. > i start writing, then i want to go back a line, and then oops, and my > half written command is gone. bad. > > it would not be so bad if the half written command did not get lost.
As Philip said, this is not how fish should be behaving. If there are no matches, pressing up or down should give you the original search string. If not, that is a bug. > and maybe instead of the arrow keys some other keys can be provided to > switch lines. Sure, it's a reasonable operation. It should be possible to move up/down somehow. > > in that same area: ctrl-a and ctrl-e should only move within one line. > and essentially, all the editing features of a single line command > should be available within a line of a multiline command. Missed that one. That should be fixed. And Alt+< and Alt+> should move to the beginning/end of the buffer, just like in emacs. Thanks for bringing it up. > > just today i wanted to build a look and within it reuse a command that i > had used before. being able to activate a search at that point would > have been ideal. It might be better to have a special 'insert history search match at this point' command for that. Maybe Ctrl-r reborn? Or maybe one could use some cool magic with the read builtin. > > and, while i am at it: <enter> should not execute the command unless you > are at the end. otherwise it is not possible to add more lines to an old > command without first going to the end, to remove something to make sure > the command is incomplete, because the enter will run the command if it > is complete. Use either Alt-enter or backslash+enter to add a newline that doesn't execute the command. > > all arguments about modality aside: > multiline editing already IS a different mode. Currently it really isn't. Fish internally regards single line editing as multiline editing on a short string, just as it regards non-array variables as arrays with length one. There really is very little modality in fish. > > greetings, martin. > -- > cooperative communication with sTeam - caudium, pike, roxen and unix > offering: programming, training and administration - anywhere in the world > -- > pike programmer travelling and working in europe open-steam.org > unix system- bahai.or.at iaeste.(tuwien.ac|or).at > administrator (caudium|gotpike).org is.schon.org > Martin Bähr http://www.iaeste.or.at/~mbaehr/ > -- Axel ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Fish-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fish-users
