From: Michael Albinus <michael.albinus@gmx.de>
To: "Ævar Arnfjörð Bjarmason" <avar@booking.com>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>, 24478@debbugs.gnu.org
Subject: bug#24478: 25.1; Regression in 25.1: .tramp_history files are littered in non-$HOME working directories
Date: Thu, 22 Sep 2016 20:02:59 +0200 [thread overview]
Message-ID: <87zimzke24.fsf@gmx.de> (raw)
In-Reply-To: <8737kuan39.fsf@booking.com> ("Ævar Arnfjörð Bjarmason"'s message of "Tue, 20 Sep 2016 12:21:14 +0200")
Ævar Arnfjörð Bjarmason <avar@booking.com> writes:
Hi,
> There's a regression in 25.1 introduced by 1e04ea9 (although that seems
> to also have fixed an issue): Now tramp-histfile-override is set to
> ".tramp_history", which is good, but I would expect it to be created in
> $HOME on remote hosts.
>
> Instead when I e.g.:
>
> 1. C-x C-f //ssh:<hostname>:/usr/local/git_tree/sysadmin/
> 2. Run e.g. magit to make a commit
> 3. I end up with:
>
> $ echo $PWD/.tramp_history
> /usr/local/git_tree/sysadmin/.tramp_history
> $ wc -l !$
> wc -l $PWD/.tramp_history
> 34 /usr/local/git_tree/sysadmin/.tramp_history
Most of the shells I know off use the home directory, when you specify
just the relative file name ".tramp_history".
> From reading https://debbugs.gnu.org/cgi/bugreport.cgi?bug=20446 and
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=19731#56 this seems like
> an unintended bug.
>
> Just setting:
>
> (setq tramp-histfile-override "~/.tramp_history")
>
> Works for me. Now it's always created in ~.
I have thought about this, when I was fixing bug#19731. Unfortunately,
there exist shells which cannot expand "~/". Other shells cannot expand
"$HOME/". So I really don't know a robust default we could offer.
Maybe one should give this problem more emphasis in the Tramp
manual. But who reads manuals?
Best regards, Michael.
next prev parent reply other threads:[~2016-09-22 18:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 10:21 bug#24478: 25.1; Regression in 25.1: .tramp_history files are littered in non-$HOME working directories Ævar Arnfjörð Bjarmason
2016-09-22 18:02 ` Michael Albinus [this message]
2016-10-10 10:38 ` Eli Zaretskii
2016-10-10 11:14 ` Ævar Arnfjörð Bjarmason
2016-10-11 13:54 ` Michael Albinus
2016-10-11 14:34 ` Ævar Arnfjörð Bjarmason
2016-10-11 14:44 ` Michael Albinus
2016-10-11 14:47 ` Ævar Arnfjörð Bjarmason
2016-10-12 14:05 ` Michael Albinus
2016-10-13 14:51 ` Michael Albinus
2016-10-13 15:18 ` Ævar Arnfjörð Bjarmason
2016-10-13 16:30 ` Michael Albinus
2016-10-15 10:38 ` Michael Albinus
2016-10-22 16:55 ` Michael Albinus
2016-10-23 23:29 ` Glenn Morris
2016-10-24 7:09 ` Michael Albinus
2016-10-24 13:10 ` Michael Albinus
2016-10-24 13:54 ` Ævar Arnfjörð Bjarmason
2016-10-24 14:32 ` 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=87zimzke24.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=24478@debbugs.gnu.org \
--cc=avar@booking.com \
--cc=avarab@gmail.com \
/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).