From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: jporterbugs@gmail.com, 65685@debbugs.gnu.org
Subject: bug#65685: 29.1; Inconsistent behavior of quoted file name "/:~" across platforms
Date: Sun, 15 Oct 2023 12:36:00 +0300 [thread overview]
Message-ID: <83wmvop6rj.fsf@gnu.org> (raw)
In-Reply-To: <871qdwnyw8.fsf@gmx.de> (message from Michael Albinus on Sun, 15 Oct 2023 09:11:19 +0200)
> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: jporterbugs@gmail.com, 65685@debbugs.gnu.org
> Date: Sun, 15 Oct 2023 09:11:19 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> Hi Eli,
>
> >> >> The only difference I could think of is that the directory Emacs uses
> >> >> here has whitespace in its name (see my original report), whereas on
> >> >> Windows 10 it probably doesn't.
> >> >
> >> > FTR, if I use a directory with spaces in its name, it fails for me as
> >> > well. I'm now debugging ...
> >>
> >> It looks, like it is a problem in the test case code
> >> itself. abbreviate-file-name does not work as I expect in this
> >> combination.
> >
> > Can you tell more about this? I'm surprised any file-related
> > primitive in Emacs cares about whitespace in file names.
>
> Perhaps we have uncovered a bug in abbreviate-file-name, don't
> know. I'll check when time permits.
I'd like to understand this sooner rather than latter. Can you show
some simple recipe which fails under these conditions?
> However, it isn't related to the change in question of this bug report,
> handling expand-file-name for constructs like "/:~..." and
> "/ssh:host:/:~...". abbreviate-file-name has been used to create a
> temporary test file for this case, it isn't target of the test itself.
I applied your changes to the test, and it passes after that, thanks.
next prev parent reply other threads:[~2023-10-15 9:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 19:22 bug#65685: 29.1; Inconsistent behavior of quoted file name "/:~" across platforms Jim Porter
2023-10-03 11:22 ` Michael Albinus
2023-10-10 4:27 ` Jim Porter
2023-10-13 14:26 ` Michael Albinus
2023-10-14 0:31 ` Jim Porter
2023-10-14 7:42 ` Michael Albinus
2023-10-14 7:42 ` Eli Zaretskii
2023-10-14 7:48 ` Michael Albinus
2023-10-14 10:56 ` Michael Albinus
2023-10-14 11:25 ` Eli Zaretskii
2023-10-14 14:29 ` Michael Albinus
2023-10-14 16:48 ` Michael Albinus
2023-10-14 19:07 ` Eli Zaretskii
2023-10-15 7:11 ` Michael Albinus
2023-10-15 9:36 ` Eli Zaretskii [this message]
2023-10-15 9:50 ` Michael Albinus
2023-10-15 9:58 ` Eli Zaretskii
2023-10-15 10:29 ` Michael Albinus
2023-10-15 20:12 ` Mattias Engdegård
2023-10-16 7:07 ` Michael Albinus
2023-10-16 7:30 ` Mattias Engdegård
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=83wmvop6rj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65685@debbugs.gnu.org \
--cc=jporterbugs@gmail.com \
--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).