On Tue, Aug 22, 2006 at 03:17:56AM +0200, Axel Liljencrantz wrote: > > that said, half of the time i find myself trying to use fish style > > history in a bash. > I won't be happy until you never find yourself using bash. :)
on my notebook currently the only use of bash is for root, since i am not yet sure i want to trust fish that much. on the other hand, the more i use fish the more i like it, and thus the more i stay away from the root shell, and that's actually good thing. the other thing that keeps me from using fish for root is the lack of a kill builtin. the reason for that is, that sometimes the machine can be so loaded that forking a new command fails. in such situations a builtin kill function is potentially the only way to potentially stop runaway processes. and then there are a number of debian servers where i am not the main administrator,where i would first need to get consent to be allowed to install fish, since fish is not in debian stable. (but once etch is out that will be easier to argue) > > namely for a command that just prints the history to stdout, > The $history environment variable contains the last 10 entries form ahh, didn't think about that one. > It would be easy to extend this to contain the entire history. that would be nice. > Would a builtin command be better? i don't think so. having the history in a variable should open up even more interesting ways to manipulate it. and in the worst case it would just take a loop to pipe all entries through grep. > 'commandline -t' should do just that. ah, yes, thanks. i saw -t but in the description above it somehow i only saw updated and missed that it also mentioned printing > That lets you use Meta-x to enter a new command, which can in turn > operate to the contents of the previous commandline. that part escapes me. how do i get the entered command to operate in the previous commandline? > Sure. Along a related path, it was suggested some time ago that event > hooks be added that are fired before a commandline command is > executed. that would be interresting. > That way a sed script could be run on the commandline before > executing it, which would transform Posix shellscript into fish > shellscript. ??? > making fish extensible enough to allow you to do things like that > would be pretty cool. indeed, i can see a lot of other uses: logging, help for beginners (paperclip style: hey, it looks like you want to change your directory, do you want to ...? ;-) > If you have a design for a complete replacemnt of the current history > search, or a separate system that completemnts the current system in a > nice way and is significantly more powerful, feel free to provide a > detailed description. i am considering to experiment in the direction of something that actually displays the matching history entries, or at least a screenful of them. btw, to implement incremental search a trigger on each keypress would be useful... 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/ ------------------------------------------------------------------------- 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
