From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Cc: Brian Inglis <Brian.Inglis@shaw.ca>
Subject: Re: [ANNOUNCEMENT] Updated: dash 0.5.12-2
Date: Thu, 16 Feb 2023 10:53:47 +0100 [thread overview]
Message-ID: <Y+39K2XWvmLrYHMg@calimero.vinschen.de> (raw)
In-Reply-To: <67b919ee-ab5e-3424-16aa-df5e9953fd89@Shaw.ca>
Hi Brian,
On Feb 15 15:31, Brian Inglis via Cygwin wrote:
> On 2023-02-15 07:05, Corinna Vinschen via Cygwin wrote:
> > On Feb 15 14:52, Corinna Vinschen via Cygwin wrote:
> > > The currently building cygwin test release 3.5.0-0.174.gd6d4436145b8
> > > contains the new code. Would you mind to build a dash for testing so we
> > > can see if and how it works?
>
> > You don't have to build a new dash. Just downgrading to
> > dash-0.5.12-1 will suffice, of course. D'oh.
> > So, as a first test, here's the result of Andrey's expression
> > with dash-0.5.12-1:
> > $ dash -c '_x=" x"; echo "${_x#${_x%%[![:space:]]*}}"'
> > x
>
> Good and quick work!
> I was still looking thru my last Cygwin build for the Unicode tables, that I
> remember being rebuilt some time ago, and to find what used them, and
> whether they were updated to Unicode 15.
>
> I'll install the test Cygwin and old dash, then prep and check a new/old
> dash release 3 in test, for release with untest when the Cygwin changes are
> released, rather than play with replacing versions and going back and forth.
That *may* be a bit early... The patches are not bugfixes, but
implementing new features. As such, you won't find them in a 3.4 bugfix
release. They will hit the light with the first 3.5.0 release only,
probably end of 2023.
Corinna
prev parent reply other threads:[~2023-02-16 9:53 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
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 [this message]
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=Y+39K2XWvmLrYHMg@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=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).