Hi Previously, fish has used a newline to separate items in the history file. This worked fine as long as fish didn't support multiline commands. I have come up with various new file formats, but the one I think I like best is for newlines inside a multiline command to be backslash escaped, i.e.
foo\ bar\ baz is a single set of commands but foo bar baz are three separate commands. For this to work, the fish syntax needs to be changed so that a backslash before a newline is ignored even when inside quotes, which is not the case today. Also, while we are at it, I think that adding a line beginning with a '#' before each command. This lets us associate e.g. a timestamp with each history entry, which could be very useful. A '#' is nice, since it means a comment in fish, so it will be ignored. This is also how bash saves timestamps in the history file. Comments are welcome. Once the history problem is fixed, the new config file reshuffle is done, and ^K and various other keyboard shortcuts are made to operate on a single line and not the entire buffer, all known fish regressions should be fixed, and one can start thinking about a new fish release. Though there should be some serious testing of multiline on different terminals before that as well. If anyone has the time, please report what terminals work and don't work with the current darcs version of fish. Also, I have added support for autoindentation to fish. Looks cool. :-) -- 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
