>>>>> "Pete" == Pete Forman <[EMAIL PROTECTED]> writes:
> Stefan Monnier writes:
>> Just guessing. I refuse to believe that someone would write
>> a shell whose history file feature cannot be turned off.
> The POSIX/UNIX rules for shells mandate that history cannot be turned
> off, unless the shell is invoked non-interactively :-(
Can you point me to a precise quote (maybe in the SUSv2 spec) ? I can't
really believe what you're telling me since the SUSv2 page defining `sh'
(http://www.opengroup.org/onlinepubs/7908799/xcu/sh.html) presents HISTFILE
and HISTSIZE, both of which are directly relevant. I.e. the user can set
HISTSIZE to work around the poor Tramp interaction (although as I said in
another article, Tramp probably shouldn't use here-documents, which would
solve the main part of the problem). And Tramp could set HISTFILE to
/dev/null so clearly, there is a way to turn off the history file.
Maybe the spec does not allow turning off the history feature, but that's
not relevant here. We're only discussing the use of a history *file*.
Better yet the specification of the shell command language
(http://www.opengroup.org/onlinepubs/7908799/xcu/chap2.html) says the
following:
set - Set or Unset Options and Positional Parameters
SYNOPSIS
set [-abCefmnuvx][-h][-o option][argument...]
set [+abCefmnuvx][+h][-o option][argument...]
set --[argument...]
set -[argument...]
[...]
-o option
[...]
nolog
Prevent the entry of function definitions into the command
history. See Command History List.
so clearly, there is a way to turn off the feature.
Stefan
