On Sat, 17 Mar 2001, Tom Roche wrote:
> On Sat, 17 Mar 2001, Tom Roche wrote:
>>> * is tramp writing to this file?
>
> [EMAIL PROTECTED] 17 Mar 2001 21:18:10 +0100
>> No, Tramp itself is not writing to the file, but I think the shell
>> is. If you read the documentation for ksh and tell me how to turn
>> off the history, I'll put that code in Tramp.
>
> It's not immediately obvious. I see each of two different versions
> in several URLs.
Excuse me if this is very stupid, but why don't you just read the man
page of _your_ ksh? Log in on the remote host in question and type
`man ksh'...
> http://www.ntua.gr/cgi-bin/man-cgi?ksh+1
>> Command Re-entry
>> The text of the last HISTSIZE (default 128) commands entered from a
>> terminal device is saved in a history file. The file
>> $HOME/.sh_history is used if the HISTFILE variable is not set or if
>> the file it names is not writable.
>
> which suggests that there's no way to say "no HISTFILE, please."
Maybe HISTSIZE=0 works?
> Do you have any ideas about how to set "appropriate privileges" for
> the duration of the session?
I think you _don't_ want the privileges. W/o privileges, the file is
not written.
I guess you could do this:
rm .sh_history
touch .sh_history
chmod a-w .sh_history
But please try one of the other suggestions first, it would be more
general to do it from within Tramp.
>> (There is already code for turning off the bash history.)
>
> Perhaps this code might work with ksh also?
You have just discovered that it doesn't work, else you wouldn't have
the .sh_history file. (Maybe I should have explicitly said that the
code is in the released version and is active by default, and it
cannot be turned off.)
kai
--
Be indiscrete. Do it continuously.
