Very good... thanks, John and Dave. And I agree about moving oft-used bits of code into functions... Quoting John Houck <houck_at_email.domain.hidden > On Wed, Mar 28, 2007 at 12:12 -0500, rgibson_at_email.domain.hidden>> I'm often debugging and have to repetitively cut/paste large amounts of code >> onto the ISIS command line. Is there a simple way to do this? > > In general, I would recommend looking for ways to turn > often-used bits of code into functions that take generic > arguments. Those functions can then be loaded at startup by > your $HOME/.isisrc file or perhaps loaded on-demand through the > "autoload" feature. > >> What I want is to have a text file with my "Lotsa code" and tell ISIS to >> execute that text file just as if I had pasted it to the command line. >> > > I think the ".source" command does what you want: > > .source > > SYNOPSIS > read slang commands from a file > > USAGE > .source filename > > DESCRIPTION > This function is very similar to the .load shortcut except that > lines from the file are interpreted as though they had been > typed at the command line -- all command shortcuts are > available and variables need not be declared before use. > > SEE ALSO > .load, evalfile > > > Thanks, > -John > ---- > You received this message because you are > subscribed to the isis-users list. > To unsubscribe, send a message to > isis-users-request_at_email.domain.hidden> with the first line of the message as: > unsubscribe > > ---- You received this message because you are subscribed to the isis-users list. To unsubscribe, send a message to isis-users-request_at_email.domain.hiddenwith the first line of the message as: unsubscribeReceived on Wed Mar 28 2007 - 14:14:21 EDT
This archive was generated by hypermail 2.2.0 : Fri Apr 06 2007 - 11:02:28 EDT