From: Andreas Schwab <schwab@suse.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 21454@debbugs.gnu.org, Tino Calancha <tino.calancha@gmail.com>
Subject: bug#21454: 25.1.50; `parse-colon-path' fails with file names containing multiple consecutive "/"
Date: Tue, 25 Jun 2019 18:29:31 +0200 [thread overview]
Message-ID: <mvm1rzhwrv8.fsf@suse.de> (raw)
In-Reply-To: <m3woh965w1.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 25 Jun 2019 17:28:46 +0200")
On Jun 25 2019, Lars Ingebrigtsen <larsi@gnus.org> wrote:
> Tino Calancha <tino.calancha@gmail.com> writes:
>
>> Do not truncate /foo//bar to /bar/
>> * lisp/files.el (parse-colon-path): Use substitute-env-vars and
>> expand-file-name instead of substitute-in-file-name (Bug#21454).
>
> The bug report was slightly unclear, but I think the taste case was
>
> (parse-colon-path "/foo//bar/baz")
> => ("/bar/baz/")
>
> and that being a mistake? But I'm not sure it is -- In Emacs, if you do
> that in, say, find-file, you'll end up in /bar/baz, and that's by
> design.
For file names coming from outside the double slash should not be
special. For example, `emacs foo//bar' visits the file `foo/bar', not
`/bar'.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2019-06-25 16:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 11:15 bug#21454: 25.0.50; `parse-colon-path' fails with paths containing consecutive directory separators Tino Calancha
2015-09-10 12:48 ` bug#21454: (no subject) Tino Calancha
2016-04-24 17:26 ` bug#21454: 25.0.93; `parse-colon-path' over dirs with 2 consecutive dir sep Tino Calancha
2016-09-13 8:55 ` bug#21454: 25.1.50; `parse-colon-path' fails with file names containing multiple consecutive "/" Tino Calancha
2016-09-13 9:16 ` Andreas Schwab
2016-09-13 9:40 ` Tino Calancha
2017-08-31 1:09 ` npostavs
2019-06-25 15:28 ` Lars Ingebrigtsen
2019-06-25 16:29 ` Andreas Schwab [this message]
2020-08-12 12:54 ` Lars Ingebrigtsen
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=mvm1rzhwrv8.fsf@suse.de \
--to=schwab@suse.de \
--cc=21454@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=tino.calancha@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).