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 :-(
--
Pete Forman
"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
On Wed, 11 Apr 2001, Stefan Monnier wrote:
Oh no! Here-documents!
Kai, is there a good reason for using here documents here ?
Maybe there was, once upon a time. I have now changed it and did a
quick test. Seems to work.
New version in CVS. Please test.
kai
--
Be indiscrete. Do it
Update of /services/emacs-rcp/cvsroot/tramp/lisp
In directory lucy:/export/home/grossjoh/work/kai/tramp-devel/tramp/lisp
Modified Files:
tramp.el ChangeLog
Log Message:
(tramp-handle-write-region): Don't use here document,
just send encoded file on stdin. Suggested by Stefan Monnier.
"Pete" == Pete Forman [EMAIL PROTECTED] writes:
It is moot as to whether /dev/null is suitable for HISTFILE. While it
does have read and write permissions I would infer that the shell
expects to be able to read back what is written. A robust
implementation should be able to cope but can we
Stefan Monnier writes:
On the other hand `HISTFILE=/dev/null /bin/ksh' will not work if
the user's SHELL is not bourne-like, which is more annoying.
Yes I do realize, I was simplifying in that message.
And I don't think we can rely on /usr/bin/env being available, so
it's not clear how
On 12 Apr 2001, Stefan Monnier wrote:
On the other hand `HISTFILE=/dev/null /bin/ksh' will not work if the
user's SHELL is not bourne-like, which is more annoying. And I don't
think we can rely on /usr/bin/env being available, so it's not clear how
we can reliably set the env var before
Stefan Monnier writes:
Stefan On the other hand `HISTFILE=/dev/null /bin/ksh' will not work if
Stefan the user's SHELL is not bourne-like, which is more annoying.
In csh-like shells, you can often do
env HISTFILE=/dev/null /bin/ksh
/usr/bin/env is available on Solaris, at
"Ted" == Ted Stern [EMAIL PROTECTED] writes:
/usr/bin/env is available on Solaris, at least.
Experience shows you can't rely on it being available.
And in any case it's not much better than
`ksh -c "HISTFILE=/dev/null exec ksh"'
Stefan
[EMAIL PROTECTED] 12 Apr 2001 17:30:49 +0200
Anyway, could somebody with a ksh try various things to turn off its
history?
How soon they forget :-)
http://www.mail-archive.com/emacs-rcp@ls6.cs.uni-dortmund.de/
has a thread ".sh_history problem" that started Sat, 17 Mar 2001. It
has 9 posts
[EMAIL PROTECTED] 12 Apr 2001 18:26:16 +0200
Is there any reason not to send "HISTFILE=/dev/null" during the
connection initialization?
In my experience setting HISTFILE=/dev/null did not work: ksh merely
made a tempfile.
This might be n=1, however. Perhaps someone else can try some things
on
For example, what happens if we do "HISTSIZE=0" in addition to
"unset HISTFILE"?
IIRC I tried that, and it didn't work: ksh made temp files.
Have you tried /dev/null ?
Also since the current code doesn't use here-documents any more, your
.sh_history file should grow much slower now (it
[EMAIL PROTECTED] writes:
In my experience setting HISTFILE=/dev/null did not work: ksh merely
made a tempfile.
Of course, this still uses up disk space, but now that only actual commands
rather than file contents go into the history file, it's less of a concern.
The remaining question is:
[EMAIL PROTECTED] writes:
In my experience setting HISTFILE=/dev/null did not work: ksh
merely made a tempfile.
"Stefan Monnier" [EMAIL PROTECTED] 12
Apr 2001 17:53:49 -0400
Of course, this still uses up disk space, but now that only actual
commands rather than file contents go into the
Re the .kshrc hack:
For your reference, here is what I do:
In ~/.profile, add the line
ENV=$HOME/.kshrc; export ENV
In ~/.cshrc, add the line
setenv ENV ~/.kshrc
Flogging the dead horse ... if you ever run bash or zsh, also add to your
~/.{bash,zsh}rc files:
Harry Putnam [EMAIL PROTECTED] 12 Apr 2001 16:10:37 -0700
Is [SMB] too different from the other protocols tramp understands?
Preface my remarks with "not being a tramp expert," but ...
I believe SMB is the next level down from the protocols tramp uses. To
put it rather non-technically (and
Update of /services/emacs-rcp/cvsroot/tramp/lisp
In directory lucy:/export/home/grossjoh/work/kai/tramp-devel/tramp/lisp
Modified Files:
tramp.el ChangeLog
Log Message:
(tramp-open-connection-setup-interactive-shell): Posix
shells don't allow you to turn off the history, so we redirect
On Thu, 12 Apr 2001, Tom Roche wrote:
[EMAIL PROTECTED] 12 Apr 2001 17:30:49 +0200
For example, what happens if we do "HISTSIZE=0" in addition to
"unset HISTFILE"?
IIRC I tried that, and it didn't work: ksh made temp files.
What was their size? So should HISTFILE be left at a default
Kai Grossjohann [EMAIL PROTECTED] Fri, 13 Apr 2001
01:45:27 +0200
Log Message:
(tramp-open-connection-setup-interactive-shell): Posix shells don't
allow you to turn off the history, so we redirect it to an innocuous
file and limits that file's size as much as possible.
I can try this out.
On 12 Apr 2001, Harry Putnam wrote:
Has anyone every fiddled with getting tramp to work over smb
protocol?
[EMAIL PROTECTED] 13 Apr 2001 01:28:16 +0200
Tramp wants a login shell and expects to be talking to a Unixish
system on the remote end. You could install an sshd and a bash on
the
On 12 Apr 2001, Harry Putnam wrote:
Has anyone every fiddled with getting tramp to work over smb
protocol?
Tramp wants a login shell and expects to be talking to a Unixish
system on the remote end. You could install an sshd and a bash on the
remote system, and if it looks sufficiently
[EMAIL PROTECTED] (Kai Grojohann) writes:
On 12 Apr 2001, Harry Putnam wrote:
Has anyone every fiddled with getting tramp to work over smb
protocol?
Tramp wants a login shell and expects to be talking to a Unixish
system on the remote end. You could install an sshd and a bash on the
22 matches
Mail list logo
