From: Philipp Stephani <p.stephani2@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 53847@debbugs.gnu.org
Subject: bug#53847: 28.0.91; Tramp SSHFS: incorrect remote home directory
Date: Wed, 9 Mar 2022 10:17:24 +0100 [thread overview]
Message-ID: <CAArVCkS3XaZTVYBJV6Dmr6X0=N3Cd6ccGf2sbdA8jNGAkNsxRw@mail.gmail.com> (raw)
In-Reply-To: <871r0ct40m.fsf@gmx.de>
Am Mi., 9. Feb. 2022 um 17:10 Uhr schrieb Michael Albinus
<michael.albinus@gmx.de>:
>
> Philipp Stephani <p.stephani2@gmail.com> writes:
>
> Hi Philipp,
>
> > To reproduce this, you need two GNU/Linux machines with the same user
> > name but different home directories. Assume that on host 1 the user's
> > home directory is /home1/user, and that on host 2 the user's home
> > directory is /home2/user. With the SSH protocol, home directory
> > expansion works as expected:
> >
> > However, this fails with SSHFS:
>
> Tilde expansion is not possible for sshfs (and adb, rclone) methods of
> Tramp. I've added a check, and Tramp raises an error now when it detects
> a tilde. Pushed to master.
>
Thanks, but would it maybe be possible to find a better solution? I've
been using SSHFS for a while now, and this particular issue is pretty
annoying in practice. How about any of the following:
- When connecting over SSHFS, ask the remote host (via SSH) for the
home directory and cache the result.
- Allow the user to configure a per-host static home directory (i.e.
just a customizable mapping from hosts + users to home directories). I
regularly only connect to 2 hosts with known hostnames and home
directories, so at least for me maintaining such a mapping would be
feasible.
WDYT?
next prev parent reply other threads:[~2022-03-09 9:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 14:30 bug#53847: 28.0.91; Tramp SSHFS: incorrect remote home directory Philipp Stephani
2022-02-09 16:10 ` Michael Albinus
2022-02-11 8:44 ` Michael Albinus
2022-03-09 9:17 ` Philipp Stephani [this message]
2022-03-09 9:33 ` Michael Albinus
2022-03-10 11:37 ` Michael Albinus
2022-03-18 16:53 ` Philipp Stephani
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='CAArVCkS3XaZTVYBJV6Dmr6X0=N3Cd6ccGf2sbdA8jNGAkNsxRw@mail.gmail.com' \
--to=p.stephani2@gmail.com \
--cc=53847@debbugs.gnu.org \
--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).