[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: |
Lars Ingebrigtsen |
Subject: |
bug#21454: 25.1.50; `parse-colon-path' fails with file names containing multiple consecutive "/" |
Date: |
Tue, 25 Jun 2019 17:28:46 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
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.
But I may have misread what this was about...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
- bug#21454: 25.1.50; `parse-colon-path' fails with file names containing multiple consecutive "/",
Lars Ingebrigtsen <=