On 09 Jan 2001, Kai Grojohann wrote:
Good. Then unless somebody says that "set +o history" is useful for
ksh, say, then I'll replace it.
I have now replaced `set +o history' with `unset HISTFILE'. I hope it
works.
kai
--
Be indiscrete. Do it continuously.
Kai Tramp tries to turn history off altogether. Search tramp.el for
Kai `hist' and find this code:
Kai (tramp-message 9 "Waiting 30s for `set +o history'")
...
Yup, found it. Used edebug-defun to trace tramp's startup and insure it was
getting executed. Once the process
Skip Montanaro writes:
Could this be a feature of bash 2.x? On the remote machine I'm
still running 1.14.7(1). In fact, that appears to be it. The bash
man page on that machine doesn't mention "history" as a possible
value for the set command's -o flag. I'll have to dink around and
Pete The Linux installations that I've seen do have bash 2.03 in
Pete /bin/bash2. I would suggest modifying tramp-find-shell to look
Pete for "bash2" between "ksh" and "bash".
It's not clear that would help me. I have a number of RH-derived systems.
Here's what I see:
RH5.2:
Bash 1.14.7 doesn't understand either "set +o history" or the HISTIGNORE
environment variable. I think the best way to suppress bash's history stuff
for all versions is to set HISTFILE to /dev/null. Appended is a patch that
works for me on the system with the original problem (RH5.2). I also
Skip Montanaro writes:
Pete The Linux installations that I've seen do have bash 2.03
Pete in /bin/bash2. I would suggest modifying
Pete tramp-find-shell to look for "bash2" between "ksh" and
Pete "bash".
It's not clear that would help me. I have a number of
On Tue, 9 Jan 2001, Skip Montanaro wrote:
Kai Does it work to say "unset HISTFILE" to turn off bash1's
Kai history saving mechanism?
That would work as well.
Good. Then unless somebody says that "set +o history" is useful for
ksh, say, then I'll replace it.
kai
--
~/.signature
Kai Does it work to say "unset HISTFILE" to turn off bash1's history
Kai saving mechanism?
That would work as well.
Skip
On Mon, 8 Jan 2001, Skip Montanaro wrote:
Is anyone else using HISTIGNORE to squelch tramp's chit chat? If
so, what are you using? Where are you setting HISTIGNORE? I don't
suppose tramp could be coaxed into doing this automagically could
it?
Does it work to say "unset HISTFILE" to turn
I set HISTIGNORE as
HISTIGNORE='*tramp_exit_status*:*tramp_file_attributes*'
and export it in my ~/.bash_profile file but I still get lots of tramp turds
flooding out all the useful interactive commands in my history list, e.g.
lines like
ls -d
10 matches
Mail list logo
