From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: crocket <crockabiscuit@gmail.com>, 19731@debbugs.gnu.org
Subject: bug#19731: 24.4; /dev/null is deleted by tramp-sh.el
Date: Mon, 02 Feb 2015 13:44:00 -0500 [thread overview]
Message-ID: <jwvd25sf94k.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <87d25sjwgj.fsf@gmx.de> (Michael Albinus's message of "Mon, 02 Feb 2015 14:04:44 +0100")
> Well, I'm kind of conservative. Setting HISTFILE to /dev/null is the
> default for years, and your report is the first one about this problem.
It seems like a plain bug for bash to do what it does (does it also
turn a symlink into a plain file? wouldn't that also be a bug?), but
I wonder: what could Tramp do instead of setting HISTFILE to /dev/null?
Could unsetting it result in the same behavior (i.e. not save Tramp's
commands to any file)?
Stefan
next prev parent reply other threads:[~2015-02-02 18:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-30 5:18 bug#19731: 24.4; /dev/null is deleted by tramp-sh.el crocket
2015-01-30 9:38 ` crocket
2015-01-30 9:41 ` crocket
2015-02-02 11:44 ` Michael Albinus
[not found] ` <CAL0=0H0i02hc96VRz4HFnS9ztr2-1SxaykZiJ6mqPQxm5h2aag@mail.gmail.com>
[not found] ` <87mw4wjyqi.fsf@gmx.de>
2015-02-02 12:22 ` crocket
2015-02-02 12:45 ` Michael Albinus
2015-02-02 12:46 ` crocket
2015-02-02 13:04 ` Michael Albinus
2015-02-02 14:18 ` crocket
2015-02-02 15:25 ` Michael Albinus
2015-02-02 18:44 ` Stefan Monnier [this message]
2015-02-02 19:50 ` Michael Albinus
2015-02-02 20:08 ` Glenn Morris
2015-02-03 3:06 ` crocket
2015-02-03 8:34 ` Michael Albinus
2015-02-03 9:10 ` Andreas Schwab
2015-02-03 9:23 ` Michael Albinus
2015-02-03 16:54 ` Glenn Morris
2015-02-06 11:01 ` Alad Wenter
2015-02-08 10:05 ` Michael Albinus
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvd25sf94k.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=19731@debbugs.gnu.org \
--cc=crockabiscuit@gmail.com \
--cc=michael.albinus@gmx.de \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).