From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: dash 0.5.12-2
Date: Mon, 13 Feb 2023 12:03:31 -0700 [thread overview]
Message-ID: <8a583e14-b413-d1a2-35d9-e76f73a4b338@Shaw.ca> (raw)
In-Reply-To: <6810586169.20230213204858@yandex.ru>
On 2023-02-13 10:43, ASSI via Cygwin wrote:
> Corinna Vinschen via Cygwin writes:
>> On Feb 12 22:03, Cygwin dash Co-Maintainer wrote:
>>> The following packages have been upgraded in the Cygwin distribution:
>>>
>>> * dash 0.5.12-2
>>>
>>> This package is being upgraded to current as the previous release
>>> breaks existing function that may be relied on by some scripts.
>>> This release has been rebuilt disabling libc fnmatch and glob as
>>> Cygwin/winsup/newlib do not support locale dependent named character
>>> classes like glibc.
>> Can you give me an example? I'm a bit puzzled because fnmatch as well
>> as glob in Cygwin support native characters.
But not locale dependent named character classes like regexp in paths.
> AFAIU, the issue was with locale dependent character classes, not
> characters. Andrey specifically mentioned [[:space:]] in the original
> bugreport.
Specifically support in fnmatch and glob, now updated in glibc, and their use in
dash for parameter expansion in place of (gnulib?) regexp support.
>> So how do we fix in Cygwin without pulling in GLibc code?
It's fixed in release 2 which disables 0.5.12 changed default (using
[Cygwin/winsup/newlib] libc fnmatch and glob, without testing functionality),
and goes back to using its own previous default (gnulib?) regexp code for
parameter expansion which supports locale dependent named character classes.
As glibc "recently" fixed their fnmatch and glob to support locale dependent
named character classes like [[:blank:]], dash decided to use those in parameter
expansions for consistency, but not exactly clearly documented, although they
added config options to enable/disable each of libc fnmatch/glob.
Cygwin bash parameter expansion also supports locale dependent named character
classes.
$ info bash pattern
$ info sed classes
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
next prev parent reply other threads:[~2023-02-13 19:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 5:03 Cygwin dash Co-Maintainer via Cygwin-announce
2023-02-13 9:22 ` Corinna Vinschen
2023-02-13 16:38 ` Corinna Vinschen
2023-02-13 17:43 ` ASSI
2023-02-13 17:48 ` Andrey Repin
2023-02-13 19:03 ` Brian Inglis [this message]
2023-02-13 19:37 ` Corinna Vinschen
2023-02-15 13:52 ` Corinna Vinschen
2023-02-15 14:05 ` Corinna Vinschen
2023-02-15 15:56 ` Andrey Repin
2023-02-15 22:31 ` Brian Inglis
2023-02-16 9:53 ` Corinna Vinschen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8a583e14-b413-d1a2-35d9-e76f73a4b338@Shaw.ca \
--to=brian.inglis@shaw.ca \
--cc=cygwin@cygwin.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.
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).