[Info-vax] RECALL command
Chris Townley
news at cct-net.co.uk
Fri Jun 23 13:38:49 EDT 2023
On 23/06/2023 18:28, Simon Clubley wrote:
> On 2023-06-23, Chris Townley <news at cct-net.co.uk> wrote:
>> Possibly with a bit of guesswork, or by looking at the contents.
>> Personally I want to be able to search for a command I previously used,
>> as I have done for years with *nix, so actually it doesn't really matter
>> which it was.
>>
>
> With bash, it's much cleaner however, and I wish DCL had a bash-style
> incremental search facility.
>
> On Linux, I run with a command history buffer of 5,000 commands which
> means all the regular commands never expire (both daily and across
> multiple active projects), while allowing all the one-off junk to
> eventually drop out of the command history buffer automatically.
>
> One problem with your approach is that you will be saving all the
> one-off junk as well as the commands you really want to save.
>
> Simon.
>
No problem with that. Just a load of files to GREP/SEARCH for that
stupidly complex that you worked out a few days/months ago!
If anybody is interested, I added the following to my LOGIN.COM for
interactive sessions:
$ if f$search("HIST.DIR") .eqs. "" then create/dire/log [.HIST]
$ hstnm = f$cvtime(f$getjpi("", "LOGINTIM"), "COMPARISON", "DATE") -
+ "_" + f$extract(0, 5, f$cvtime(f$getjpi("", -
"LOGINTIM"), "COMPARISON", "TIME")) - ":" + ".LIS"
$ hstnm = f$trnlnm("sys$login") - "]" + ".HIST]HST_''hstnm'"
$ lo*gout == "pipe recall/out=''histname' ; logouts /full "
On a home machine, could possibly add to SYLOGIN.COM
--
Chris
More information about the Info-vax
mailing list