Forgot reply-to-list again. Relevant parts of of disscusion (with Radu's permission):
On Fri, Jul 24, 2009 at 13:20, Beni Cherniavsky<[email protected]> wrote: ... > The fish name for $$ is %self: ... > The logic behind the notation is that in fish, % expands to process IDs. > [There is a small downside to reserving "%self" - it means you can't > use it to find the PIDs of programs whose names start with "self". > Maybe "%%" would be a better notation?] > On Fri, Jul 24, 2009 at 13:46, Radu Benea<[email protected]> wrote: > It's just that I sometimes type an awful lot of commands trying to find the > correct syntax for something and just need the last command remembered in > history (the correct one) > Like a few days ago I tried to find the correct way to make a flv file with > mencoder and I tried like 50 variants till I was satisfied, I could safely > paste just the last command in a shell which remembers history and forget > about the rest, so I don't have so many useless items in history. > > Best regards, > Radu > On Sun, Jul 26, 2009 at 15:03, Beni Cherniavsky<[email protected]> wrote: > Usually such junk commands don't bother me. > Next time I need them, I'd type "mencoder <Up>" and get the last such > command, presumably the working one. Also, after re-using the right command > several times, it's kept in the front of the history, while unused junk > slows drifts away. > It is a problem if I search by the wrong feature, e.g. a movie name instead > of "mencoder" - then I might hit a wrong command if the last working command > wasn't for this movie. > > Idea: maybe fish could detect automatically commands that should not be > recorded? > - Commands with syntax errors? > - Commands that exit with non-zero status? > - Commands you have killed with Ctrl+C? > > (In fact, they must be recorded, if only to allow you to press <Up> and fix > them. > But they could get some kind of lower priority, or some visible "this failed > last time" marking.) > > P.S. if you rely on history to record long-researched commands, consider > saving them as functions. It's easier than it sounds - see "funced" and > "funcsave". > -- Beni <[email protected]> ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Fish-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fish-users
