On Sat, 17 Mar 2001, Tom Roche wrote:
> [EMAIL PROTECTED] 18 Mar 2001 00:11:04 +0100
>
> Umm ... I may not be such a skilled user, but I _do_ know how to
> read a manpage :-)
*blush*
> On Sat, 17 Mar 2001, Tom Roche wrote:
>>> 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?
>
> Worth a shot. Perhaps I should make clearer:
>
>> it would be more general to do it from within Tramp.
>
> How do I "do it from within Tramp"? I think I know what needs to
> happen: after login I need to utter
>
> set HISTSIZE=0
>
> or
>
> set HISTFILE=/dev/null
>
> or whatever. How do I make Tramp do that? I'm looking for something
> like tramp-utter-this-after-login-command, and I don't see anything.
> Must I hack tramp.el?
Well, of course you can hack tramp.el. But you can also try it out
outside of Tramp, by logging in to the remote host, starting ksh (the
same that Tramp uses), send the command you want to send (to turn off
history), then send some more commands, then exit the ksh, then see if
the history has been saved or not.
Fwiw, ksh syntax is "HISTSIZE=0" and "HISTFILE=/dev/null", I think,
without `set'.
Maybe you could also look at the `set' ksh builtin. Sometimes that
offers you a way to turn on/off such features, too. Hypothetical
example: `set -h' turns history off, `set +h' turns it on.
Once I know what to do, I'll patch tramp.el to send the command in
question.
If you want to hack it yourself, feel free to go ahead. Search for
HISTFILE in tramp.el to find the right spot.
kai
--
Be indiscrete. Do it continuously.
