From: Michael Albinus <michael.albinus@gmx.de>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: 24478@debbugs.gnu.org, Ted Zlatanov <tzz@lifelogs.com>
Subject: bug#24478: 25.1; Regression in 25.1: .tramp_history files are littered in non-$HOME working directories
Date: Thu, 13 Oct 2016 16:51:41 +0200 [thread overview]
Message-ID: <8737k08fpe.fsf@gmx.de> (raw)
In-Reply-To: <87mvi9ll1j.fsf@gmx.de> (Michael Albinus's message of "Wed, 12 Oct 2016 16:05:44 +0200")
Michael Albinus <michael.albinus@gmx.de> writes:
Hi Ævar,
> I've tried it with several configurations, but I could not reproduce the
> problem locally. I suppose this behaviour is related to the used shell
> on the remote host. What is /bin/sh on your remote machine?
For the records, today I could reproduce the problem. I had to set
/bin/bash explicitely as remote shell.
Let's see, whether I could find a proper solution, compliant to all
bug#24478, bug#20446, bug#19731, bug#17295. And it is always bash, which
causes problems!
Best regards, Michael.
next prev parent reply other threads:[~2016-10-13 14:51 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
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 [this message]
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=8737k08fpe.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=24478@debbugs.gnu.org \
--cc=avarab@gmail.com \
--cc=tzz@lifelogs.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).