On 9/22/06, Martin Bähr <[EMAIL PROTECTED]> wrote: > On Fri, Sep 22, 2006 at 11:21:29AM +0300, Beni Cherniavsky wrote: [Philip Ganchev wrote:] > > > I think the history is conceptually a builtin, because you can't set > > > it (and should not be able to). > > Why shouldn't I set it? > > yes, i also would like to be able to add commands to the history with > out executing them. often i am working on a command, then i realize i > need to do something else first. at that point it would be nice to > add the command to the history to serve as memory and be able to come > back to it later.
Perhaps another reason why it should be a command is that as a variable it becomes useless, supposedly because of the large number of entries which builds up fast. I don't know what is the maximum number of arguments, but this is what happens: fish> echo $history | more fish: Failed to execute process "/bin/echo" execve: Invalid argument fish> count $history fish: Failed to execute process "/usr/local/bin/count" execve: Invalid argument fish> count "$history" fish: Failed to execute process "/usr/local/bin/count" execve: Invalid argument fish> wc -l .config/fish/fish_history 22279 .config/fish/fish_history Hurray for the fish_history file! (Actually, I think the file should be called .config/fish/history, because the "fish_" part is cacophonous. The same with "fish_inputrc" and "fish_read_history".) ------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/fish-users
