From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Jim Porter <jporterbugs@gmail.com>, 65685@debbugs.gnu.org
Subject: bug#65685: 29.1; Inconsistent behavior of quoted file name "/:~" across platforms
Date: Sat, 14 Oct 2023 12:56:07 +0200 [thread overview]
Message-ID: <87bkd1eam0.fsf@gmx.de> (raw)
In-Reply-To: <83il79sl9a.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 14 Oct 2023 10:42:25 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
Hi Eli,
>> So with the patch you merged to Tramp, plus your other one for
>> "lisp/files.el", I think this is all working consistently now.
>
> The added test fails on MS-Windows:
>
> Test files-tests-file-name-non-special-expand-file-name-tilde condition:
> (ert-test-failed
> ((should
> (equal
> (expand-file-name nospecial)
> (expand-file-name ...)))
> :form
> (equal "/:c:/Documents and Settings/Zaretzky/Local Settings/Temp/files-testsvIKNPk/files-testse2cUFY" "c:/Documents and Settings/Zaretzky/Local Settings/Temp/files-testsvIKNPk/files-testse2cUFY")
> :value nil :explanation
> (arrays-of-different-length 92 90 "/:c:/Documents and Settings/Zaretzky/Local Settings/Temp/files-testsvIKNPk/files-testse2cUFY" "c:/Documents and Settings/Zaretzky/Local Settings/Temp/files-testsvIKNPk/files-testse2cUFY" first-mismatch-at 0)))
>
> I tried to understand the idea of the change, or even the actual root
> cause of the problem, but couldn't find that in the discussion or the
> code. It doesn't help that file-name-non-special has no doc string
> and no documentation I could find about what it's supposed to do.
>
> Let's please discuss this now, because I tend just to revert the
> change on the emacs-29 branch, as it's too late there for untested
> ideas for obscure problems.
I cannot reproduce the problem. My environment:
- MS Windows 10 VM
- MSYS2 MinGW 64-bit
- A fresh git checkout of the master branch, at commit
548bc3e3d18ea6776032ca83dafbc89e3ddb5a5a
- Emacs recompiled, it reports "GNU Emacs 30.0.50 (build 13,
x86_64-w64-mingw32) of 2023-10-14"
- Running "$ make -C test files-tests" yields
--8<---------------cut here---------------start------------->8---
Ran 113 tests, 111 results as expected, 0 unexpected, 2 skipped (2023-10-14 12:49:06+0200, 7.219525 sec)
2 skipped results:
SKIPPED files-tests-file-name-non-special--subprocess
SKIPPED files-tests-file-name-non-special-dired-compress-handler
--8<---------------cut here---------------end--------------->8---
What is the difference to your setup?
Best regards, Michael.
next prev parent reply other threads:[~2023-10-14 10:56 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 [this message]
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
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=87bkd1eam0.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=65685@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jporterbugs@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).