[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#65685: 29.1; Inconsistent behavior of quoted file name "/:~" across
From: |
Michael Albinus |
Subject: |
bug#65685: 29.1; Inconsistent behavior of quoted file name "/:~" across platforms |
Date: |
Sat, 14 Oct 2023 09:48:25 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Eli Zaretskii <eliz@gnu.org> writes:
Hi Eli,
> 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.
Please give me a day to check the situation on MS Windows. I don't
believe the change would hurt Emacs 29 in any way, handling "/:~"
doesn't happen in real life I believe. It is just a preparation for a
planned change in Eshell.
I know, "Famous last words" and alike ...
Best regards, Michael.
- bug#65685: 29.1; Inconsistent behavior of quoted file name "/:~" across platforms, Michael Albinus, 2023/10/03
- bug#65685: 29.1; Inconsistent behavior of quoted file name "/:~" across platforms, Jim Porter, 2023/10/10
- bug#65685: 29.1; Inconsistent behavior of quoted file name "/:~" across platforms, Michael Albinus, 2023/10/13
- bug#65685: 29.1; Inconsistent behavior of quoted file name "/:~" across platforms, Jim Porter, 2023/10/13
- bug#65685: 29.1; Inconsistent behavior of quoted file name "/:~" across platforms, Michael Albinus, 2023/10/14
- bug#65685: 29.1; Inconsistent behavior of quoted file name "/:~" across platforms, Eli Zaretskii, 2023/10/14
- bug#65685: 29.1; Inconsistent behavior of quoted file name "/:~" across platforms,
Michael Albinus <=
- bug#65685: 29.1; Inconsistent behavior of quoted file name "/:~" across platforms, Michael Albinus, 2023/10/14
- bug#65685: 29.1; Inconsistent behavior of quoted file name "/:~" across platforms, Eli Zaretskii, 2023/10/14
- bug#65685: 29.1; Inconsistent behavior of quoted file name "/:~" across platforms, Michael Albinus, 2023/10/14
- bug#65685: 29.1; Inconsistent behavior of quoted file name "/:~" across platforms, Michael Albinus, 2023/10/14
- bug#65685: 29.1; Inconsistent behavior of quoted file name "/:~" across platforms, Eli Zaretskii, 2023/10/14
- bug#65685: 29.1; Inconsistent behavior of quoted file name "/:~" across platforms, Michael Albinus, 2023/10/15
- bug#65685: 29.1; Inconsistent behavior of quoted file name "/:~" across platforms, Eli Zaretskii, 2023/10/15
- bug#65685: 29.1; Inconsistent behavior of quoted file name "/:~" across platforms, Michael Albinus, 2023/10/15
- bug#65685: 29.1; Inconsistent behavior of quoted file name "/:~" across platforms, Eli Zaretskii, 2023/10/15
- bug#65685: 29.1; Inconsistent behavior of quoted file name "/:~" across platforms, Michael Albinus, 2023/10/15