From: Michael Albinus <michael.albinus@gmx.de>
To: Christoph Michelbach <michelbach94@gmail.com>
Cc: 31489@debbugs.gnu.org
Subject: bug#31489: 25.3; Dired unable to open directory "/ssh:example.com"
Date: Mon, 21 May 2018 16:46:59 +0200 [thread overview]
Message-ID: <87d0xp12xo.fsf@gmx.de> (raw)
In-Reply-To: <1526907544.28371.6.camel@gmail.com> (Christoph Michelbach's message of "Mon, 21 May 2018 14:59:04 +0200")
Christoph Michelbach <michelbach94@gmail.com> writes:
Hi Christoph,
> Can't the problems be avoided by establishing that paths to tramp paths can't
> start with two slashes?
>
> To paths on Unix-like systems, you can add more slashes. So with that rule in
> place, the user could simply start weird paths with two slashes and dired could
> be changed to just add another slash to the beginning of the path if the file
> the user hit enter on is in "/".
>
> The path "/ssh:example.com:" would be passed to other functions as
> "//ssh:example.com:". When Emacs asks the OS to access "//ssh:example.com:",
> it's just the same as if it asked it to access "/ssh:example.com:".
This is changed by `substitute-in-file-name':
(substitute-in-file-name "//ssh:example.com:") => "/ssh:example.com:"
See the docstring of `substitute-in-file-name', and
(info "(emacs) Minibuffer File")
Don't worry, I'm just working on a solution for you.
Best regards, Michael.
prev parent reply other threads:[~2018-05-21 14:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 11:41 bug#31489: 25.3; Dired unable to open directory "/ssh:example.com" Christoph Michelbach
2018-05-18 15:25 ` Michael Albinus
2018-05-18 22:16 ` Christoph Michelbach
2018-05-19 18:10 ` Michael Albinus
2018-05-20 18:12 ` Christoph Michelbach
2018-05-20 18:30 ` Michael Albinus
2018-05-20 19:19 ` Christoph Michelbach
2018-05-21 17:53 ` Michael Albinus
2018-06-04 16:37 ` Michael Albinus
2018-05-21 12:59 ` Christoph Michelbach
2018-05-21 14:46 ` Michael Albinus [this message]
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=87d0xp12xo.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=31489@debbugs.gnu.org \
--cc=michelbach94@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 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.