By registering with us, you'll be able to discuss, share and private message with other members of our community.
SignUp Now!Is there any one entry I can put into the HistoryExclude variable which will exclude all invocations of a file? Using the help's example,
HistoryExclude=del;free;f:\windows\system32\notepad.exe;mydir
I still get a history entry if I issue "notepad" or "notepad.exe".
When I view the post quoted above on the web, I see, in the HistoryExclude line, a space between "notepa" and "d.exe". After posting it I edited it to make sure the spave was not there and the space does not appear in the quoted version. Still the space appears on the web version.
> which will exclude all invocations of a file? Using the help's> Is there any one entry I can put into the HistoryExclude variable
>
> HistoryExclude=del;free;f:\windows\system32\notepad.exe;mydir
>
> I still get a history entry if I issue "notepad" or "notepad.exe".
>
>vefatica wrote:
>
>
>---Quote---
>> Is there any one entry I can put into the HistoryExclude variable
>---End Quote---
> > which will exclude all invocations of a file? Using the help's
> > example,
>
>
>---Quote---
>>
>> HistoryExclude=del;free;f:\windows\system32\notepad.exe;mydir
>>
>> I still get a history entry if I issue "notepad" or "notepad.exe".
>>
>---End Quote---
>Don't specify the path. The HistoryExclude test does a wildcard match
>on the command names; if you specify a path it will *not* match a
>command missing the path.