[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#21454: 25.1.50; `parse-colon-path' fails with file names containing
|
From: |
Andreas Schwab |
|
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 |
|
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.2.90 (gnu/linux) |
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."