From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: eggert@cs.ucla.edu, stefan@marxist.se, 36940@debbugs.gnu.org
Subject: bug#36940: tests slowness and failure after recent Tramp changes
Date: Sun, 25 Aug 2019 13:26:30 +0200 [thread overview]
Message-ID: <87ftlpxz89.fsf@gmx.de> (raw)
In-Reply-To: <83mufxh820.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 25 Aug 2019 13:07:51 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
Hi Eli,
>> I think you should run the strings through
>> ucs-normalize-HFS-NFD-string before comparing them, when the
>> en/decoding is done with utf-8-hfs. Alternatively, use the facilities
>> in char-fold.el to generate a more lax regexp for your search in
>> tramp--test-check-files.
>
> As yet another possibility, avoid decomposable characters in the
> strings you use altogether. You can find out whether a given
> character CH can be decomposed like this:
>
> (get-char-code-property CH 'decomposition)
>
> For characters that have no decomposition, this should return a list
> with a single element equal to CH.
Well, tramp-test41-utf8 is intended to handle all whistles and bells
related to utf8 and Tramp. So this case shall be handled as well.
The interesting point is, that the test does *not* fail with such file
names. It is rather a regexp search in a shell output, which fails.
Best regards, Michael.
next prev parent reply other threads:[~2019-08-25 11:26 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 0:28 bug#36940: tests slowness and failure after recent Tramp changes Paul Eggert
2019-08-06 12:59 ` Michael Albinus
2019-08-06 16:13 ` Paul Eggert
2019-08-06 19:16 ` Michael Albinus
2019-08-06 19:54 ` Michael Albinus
2019-08-06 23:27 ` Paul Eggert
2019-08-07 15:20 ` Michael Albinus
2019-08-07 19:36 ` Paul Eggert
2019-08-08 14:14 ` Michael Albinus
2019-08-07 21:42 ` Glenn Morris
2019-08-08 13:52 ` Michael Albinus
2019-08-10 1:39 ` Paul Eggert
2019-08-10 9:43 ` Michael Albinus
2019-08-10 20:24 ` Paul Eggert
2019-08-11 10:12 ` Michael Albinus
2019-08-14 10:31 ` Michael Albinus
2019-08-15 4:26 ` Paul Eggert
2019-08-24 1:51 ` Stefan Kangas
2019-08-24 8:08 ` Michael Albinus
2019-08-24 12:51 ` Stefan Kangas
[not found] ` <CADwFkmnZ1D-t3BchTSuUrkbkOpKG=yCH9c1ZJbkyGr9mUZrAUg@mail.gmail.com>
2019-08-25 9:27 ` Michael Albinus
2019-08-25 9:51 ` Eli Zaretskii
2019-08-25 10:07 ` Eli Zaretskii
2019-08-25 11:26 ` Michael Albinus [this message]
2019-08-25 11:39 ` Eli Zaretskii
2019-08-25 11:46 ` Michael Albinus
2019-08-25 11:58 ` Eli Zaretskii
2019-08-26 9:22 ` Michael Albinus
2019-08-26 9:59 ` Eli Zaretskii
2019-08-26 11:47 ` Michael Albinus
2019-08-26 12:54 ` Stefan Kangas
2019-08-26 14:19 ` Michael Albinus
2019-08-26 14:36 ` Stefan Kangas
2019-08-26 15:09 ` Michael Albinus
2019-08-26 15:46 ` Stefan Kangas
2019-08-26 16:43 ` Michael Albinus
2019-08-26 17:46 ` Stefan Kangas
2019-08-26 19:47 ` Michael Albinus
2019-08-27 16:34 ` Stefan Kangas
2019-08-27 16:56 ` Michael Albinus
2019-08-28 0:23 ` Stefan Kangas
2019-08-25 11:28 ` Michael Albinus
2019-08-25 11:48 ` Michael Albinus
2019-08-25 15:39 ` Paul Eggert
2019-08-25 16:34 ` Michael Albinus
2019-08-25 20:36 ` Paul Eggert
2019-08-26 8:44 ` Michael Albinus
2019-08-27 2:17 ` Paul Eggert
2019-08-27 11:03 ` Michael Albinus
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=87ftlpxz89.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=36940@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=stefan@marxist.se \
/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).