zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: dana <dana@dana.is>
Cc: Axel Beckert <abe@deuxchevaux.org>,
	Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Posted zsh 5.9
Date: Sat, 14 May 2022 21:33:58 -0700	[thread overview]
Message-ID: <CAH+w=7ZAON-uxXDmVVjj9Skh+iYxw7i+v7s+OPtmBD06mjeSwQ@mail.gmail.com> (raw)
In-Reply-To: <55919c84-74a4-4b25-97ed-9850b399561d@www.fastmail.com>

On Sat, May 14, 2022 at 3:35 PM dana <dana@dana.is> wrote:
>
> Please do. I also found a typo in NEWS i think, which i'll fix later

This one?

diff --git a/NEWS b/NEWS
index d7a817c1e..cdafd1ff5 100644
--- a/NEWS
+++ b/NEWS
@@ -49,7 +49,7 @@ negative numbers.
 The (*) expansion flag enables EXTENDED_GLOB for pattern matching.
 For example, ${(*)sample/(#b)*(pat)*/${match[1]}} uses backreferences
 even if EXTENDED_GLOB is not otherwise set.  However, this does not
-descend into nested exapansions, and doubling as (**) does not disable
+descend into nested expansions, and doubling as (**) does not disable
 EXTENDED_GLOB.

 The compinit function learnt a -w option to explain why compdump runs.


  reply	other threads:[~2022-05-15  4:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-14 20:59 dana
2022-05-14 21:50 ` Daniel Shahaf
2022-05-14 21:58   ` Daniel Shahaf
2022-05-14 22:27   ` dana
2022-05-14 23:26     ` Daniel Shahaf
2022-05-14 23:28     ` Daniel Shahaf
2022-05-14 23:50       ` dana
2022-05-15 10:36         ` Daniel Shahaf
2022-05-15 21:43           ` dana
2022-05-16 23:57   ` Phil Pennock
2022-05-21  1:31     ` Daniel Shahaf
2022-05-14 22:11 ` Axel Beckert
2022-05-14 22:31   ` dana
2022-05-15  4:33     ` Bart Schaefer [this message]
2022-05-15  6:00       ` dana
2022-05-14 23:21   ` Daniel Shahaf
2022-05-14 23:35     ` Axel Beckert
2022-05-14 23:49       ` Daniel Shahaf

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='CAH+w=7ZAON-uxXDmVVjj9Skh+iYxw7i+v7s+OPtmBD06mjeSwQ@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=abe@deuxchevaux.org \
    --cc=dana@dana.is \
    --cc=zsh-workers@zsh.org \
    /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.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).