To work around the problem of losing my interactive work which I use as the starting point for program development, I added the following to my perldl work:
Thanks, I've been wondering how to do this too.
* Edited the perldl script to change the number of lines saved in history from 50 to 250
Is that the line "@a= @a[($#a-50)..($#a)] if $#a>50 ? (line 239 of unedited perldl) If that's it, I think it would make sense to set a variable that you can edit in .perldlrc for the number 50 there. Is there any reason it's not that way already?
* Added a periodic flush of the history every 10 perldl commands so when a crash occurs I don't lose lots of typing that has to be reproduced by hand. In the .perldlrc: push @PERLDL::AUTO, 'flhist() unless ($perldl_hist_flush++ % 10);'; where the flhist() command is just a cut and paste of the existing function in the perldl program which I've attached below. --Chris
Did you paste the contents of flhist into the perldl script, or put flhist.pdl in your PDL path? Does it matter? Will it cause problems if I have 2 PDL terminals open simultaneously? Will both record to the history file, or will they overwrite each other? Thanks again, Adam _______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
