[PATCH] README, NEWS, BUGS updates

[PATCH] README, NEWS, BUGS updates

[Bart Schaefer]

[-- Attachment #1: Type: text/plain, Size: 60 bytes --]

Bringing these up to date with current significant updates.

[-- Attachment #2: Etc-5_9+.txt --]
[-- Type: text/plain, Size: 3929 bytes --]

diff --git a/Etc/BUGS b/Etc/BUGS
index 1719946b1..e238c161c 100644
--- a/Etc/BUGS
+++ b/Etc/BUGS
@@ -46,12 +46,12 @@ related, probably obsolete, vared special case for $TERM set to "emacs".
 ------------------------------------------------------------------------
 47561: [PATCH v4] vcs_info: choose backend by basedir
 ------------------------------------------------------------------------
-48091: Bug in compdescribe with matcher 'b:-=+'
+48091, 49276: Bug in compdescribe with matcher 'b:-=+'
 ------------------------------------------------------------------------
 users/26071: Strange behavior about option completion of "git push --f"
 ------------------------------------------------------------------------
 50930: If a conditional expression appears in a current-shell construct
 (such as { sleep 20 && print $? }) which is then suspended with ^Z, the
-return value of the left side of the expression is always 148 (SIGSTOP)
+return value of the left side of the expression is always 148 (SIGTSTP)
 and thus the expression is likely to be incorrectly interpreted.
 ------------------------------------------------------------------------
diff --git a/NEWS b/NEWS
index 0e726699f..80b668a6d 100644
--- a/NEWS
+++ b/NEWS
@@ -18,6 +18,15 @@ consistent and better aligned with the POSIX-2017 specification of
 `set -e`. For details on what exactly changed, see the list of
 incompatibilities in the README file.
 
+Support for named references and namespaces has been added, similar to
+those features in ksh but with some notable differences. The `nameref`
+builtin and some ksh-equivlent namespace names are available by loading
+the zsh/ksh93 module.  See the documentation of that module for more.
+
+Non-forking command substitutions with ${ ... } and ${| ... } are now
+available, and the latter extended with ${|param| ... } to return the
+result via assignment to the named param rather than always via $REPLY.
+
 Changes since 5.8.1
 -------------------
 
diff --git a/README b/README
index cb6d380aa..250b1d26e 100644
--- a/README
+++ b/README
@@ -79,6 +79,42 @@ consistent and better aligned with the POSIX-2017 specification of
       f() { { false; echo "This is printed only since 5.10." } || true }
       if f; then true; fi
 
+PCRE support is now PCRE2 by default.
+
+Parameter names may begin with a "." and follow a relaxed implementation
+of ksh namespace syntax.  Expansion of such parameters must use braces,
+that is, in ${.param.name} form.  Parameters so named are excluded from
+`typeset` and `set` output unless explicitly listed in `typeset` arguments
+or matched by a pattern with `typeset -m`.
+
+Interpretation of exclusion-patterns following alternation-patterns has
+been rationalised.  This means for example that `[[ ab = (|a*)~^(*b) ]]`
+is true where prevously it was false.
+
+Improvements to handling of terminal colors and attributes in prompts
+may change the behavior of some prompt sequences, most notably in
+cases where `esq=${(%)...}` is used to capture an escape sequence.
+
+The `which` and `functions` commands output function definitions in a
+format independent of the MULTI_FUNC_DEF option.
+
+Math context no longer interprets a leading underscore as part of a
+numeric constant.
+
+Nul and characters greater than \x77 are correctly handled by `read -d`.
+
+Return values of `sysopen` from the zsh/system module have been updated
+to be more similar to other commands in that module.
+
+The `watch' parameter and `log' command have moved to an autoloaded module.
+
+Tied parameters created with the zsh/db/gdbm module may not be re-tied
+as locals in nested function scope.  This prevents database corruption
+when a function scope ends.
+
+Many Completion/ functions have been updated to recent versions of their
+corresponding commands, so the results offered may have changed.
+
 Incompatibilities between 5.8.1 and 5.9
 ---------------------------------------
 

Re: [PATCH] README, NEWS, BUGS updates

[Mikael Magnusson]

On 10/15/23, Bart Schaefer <schaefer@brasslantern.com> wrote:
> Bringing these up to date with current significant updates.

+builtin and some ksh-equivlent namespace names are available by loading
equivalent

-- 
Mikael Magnusson

Re: [PATCH] README, NEWS, BUGS updates

[Jun T]

> 2023/10/16 6:54、Bart Schaefer <schaefer@brasslantern.com>のメール:
> 
> <Etc-5_9+.txt>

> +PCRE support is now PCRE2 by default.

"by default" may  give an impression that the old PCRE is still supported.
Actually only the PCRE2 is supported.

There are two typos:

> +builtin and some ksh-equivlent namespace names are available by loading
equivlent -> equivalent

> +is true where prevously it was false.

prevously -> previously

Re: [PATCH] README, NEWS, BUGS updates

[Bart Schaefer]

On Sun, Oct 15, 2023 at 11:39 PM Jun T <takimoto-j@kba.biglobe.ne.jp> wrote:
>
> > +PCRE support is now PCRE2 by default.
>
> "by default" may  give an impression that the old PCRE is still supported.
> Actually only the PCRE2 is supported.

So if the PCRE2 libraries aren't available, PCRE won't be
found/compiled at all?  I should have asked for clarification of this
before.

Re: [PATCH] README, NEWS, BUGS updates

[Jun T]

> 2023/10/17 8:01、Bart Schaefer <schaefer@brasslantern.com>のメール:
> 
> On Sun, Oct 15, 2023 at 11:39 PM Jun T <takimoto-j@kba.biglobe.ne.jp> wrote:
>> 
>>> +PCRE support is now PCRE2 by default.
>> 
>> "by default" may  give an impression that the old PCRE is still supported.
>> Actually only the PCRE2 is supported.
> 
> So if the PCRE2 libraries aren't available, PCRE won't be
> found/compiled at all? 

Yes, the current zsh works only with PCRE2 (does not search for old PCRE).

Re: [PATCH] README, NEWS, BUGS updates

[Oliver Kiddle]

Bart Schaefer wrote:
> diff --git a/README b/README
> index cb6d380aa..250b1d26e 100644
> --- a/README
> +++ b/README
>  
> +The `watch' parameter and `log' command have moved to an autoloaded module.

That was already done before 5.9 and dana mentioned it in the NEWS file
updates for that release.

That change is perhaps best suited to the list of incompatibilities so
perhaps that's why you missed it. I rather doubt that end users will
follow what's going on with the release notes being split between NEWS
and README. I prefer the format used by the git project for release
notes.

> +Many Completion/ functions have been updated to recent versions of their
> +corresponding commands, so the results offered may have changed.

That sentence applies for every release we ever do. Has been rather
fewer changes of that sort since 5.9 than we have in most releases.

Oliver

Re: [PATCH] README, NEWS, BUGS updates

[Bart Schaefer]

On Tue, Oct 17, 2023 at 2:26 AM Oliver Kiddle <opk@zsh.org> wrote:
>
> Bart Schaefer wrote:
> > +The `watch' parameter and `log' command have moved to an autoloaded module.
>
> That was already done before 5.9 and dana mentioned it in the NEWS file
> updates for that release.

Hm, sorry about that.  I scanned ChangeLog for things mentioned since
the version.mk touch but must have picked up on some later fix to the
module.  Can back that out.

> That change is perhaps best suited to the list of incompatibilities so
> perhaps that's why you missed it. I rather doubt that end users will
> follow what's going on with the release notes being split between NEWS
> and README. I prefer the format used by the git project for release
> notes.

I'd have no objection to this being revised ... would we leave old
stuff behind sort of like was done for ChangeLog-4.3 et al., or fold
in past history?

> > +Many Completion/ functions have been updated to recent versions of their
> > +corresponding commands, so the results offered may have changed.
>
> That sentence applies for every release we ever do. Has been rather
> fewer changes of that sort since 5.9 than we have in most releases.

I the impression it was rather a lot in terms of individual files
touched, but agree this could be dropped too.