From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Feature freeze and Tramp?
Date: Tue, 11 May 2004 20:02:07 -0500 (CDT) [thread overview]
Message-ID: <200405120102.i4C127e12749@raven.dms.auburn.edu> (raw)
In-Reply-To: <87sme7o2zu.fsf@emptyhost.emptydomain.de> (message from Kai Grossjohann on Tue, 11 May 2004 09:08:05 +0200)
Kai Grossjohann wrote:
Cool! Thanks for the fix, will incorporate this into Tramp shortly.
That leaves us with the issue of those three remaining lines which are
still somewhat of a nuisance. They can be completely gotten rid of by
setting tramp-initial-commands to
("unset HISTFILE" "unset correct" "unset autocorrect")
where the order is, of course, important. In other words "unset
HISTFILE" is pushed onto the default value.
I have customized tramp-initial-commands to the above in my personal
customizations. Can the "unset HISTFILE" ever give problems on a
remote host running an exotic shell and, if so, would the two other
"unset" commands, present in the current default, not give problems on
that same host anyway? Is there a reason not add "unset HISTFILE" to
the front of the default value, or at least, suggest doing so in
tramp-initial-commands' docstring?
("HISTFILE=" "export HISTFILE" "unset correct" "unset autocorrect")
would, I believe, make the
"HISTFILE=$HOME/.tramp_history; HISTSIZE=1; export HISTFILE; export HISTSIZE"
unnecessary, but I am afraid that some shells might not recognize "export".
However, was there any reason to use "HISTFILE=$HOME/.tramp_history;
HISTSIZE=1;" instead of simply using "HISTFILE= ; export HISTFILE" at the
same spot?
Sincerely,
Luc.
next prev parent reply other threads:[~2004-05-12 1:02 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-02 18:43 Feature freeze and Tramp? Kai Grossjohann
2004-05-02 19:19 ` David Kastrup
2004-05-03 6:20 ` Eli Zaretskii
2004-05-03 6:03 ` Kim F. Storm
2004-05-03 14:03 ` Richard Stallman
2004-05-07 21:23 ` Kai Grossjohann
2004-05-07 22:22 ` Miles Bader
2004-05-08 10:15 ` Kai Grossjohann
2004-05-10 1:33 ` Miles Bader
2004-05-10 1:39 ` Miles Bader
2004-05-08 2:34 ` Luc Teirlinck
2004-05-08 10:34 ` Kai Grossjohann
2004-05-09 1:40 ` Luc Teirlinck
2004-05-10 13:02 ` Kai Grossjohann
2004-05-11 2:49 ` Luc Teirlinck
2004-05-11 7:08 ` Kai Grossjohann
2004-05-12 0:53 ` Luc Teirlinck
2004-05-12 1:02 ` Luc Teirlinck [this message]
2004-05-12 7:32 ` Kai Grossjohann
2004-05-12 14:57 ` Luc Teirlinck
2004-05-13 6:54 ` Kai Grossjohann
2004-05-13 14:02 ` Luc Teirlinck
2004-05-15 16:36 ` Kai Grossjohann
2004-05-15 18:28 ` Luc Teirlinck
2004-05-16 9:07 ` Kai Grossjohann
2004-05-17 0:50 ` Luc Teirlinck
2004-05-17 5:11 ` Kai Grossjohann
2004-05-08 3:15 ` Luc Teirlinck
2004-05-09 2:11 ` Luc Teirlinck
2004-05-09 15:35 ` Robert J. Chassell
2004-05-09 16:26 ` Luc Teirlinck
2004-05-09 20:11 ` Stefan Monnier
2004-05-10 0:08 ` Luc Teirlinck
2004-05-09 2:34 ` Luc Teirlinck
2004-05-09 2:53 ` Luc Teirlinck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200405120102.i4C127e12749@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.