Zsh Mailing List Archive
Messages sorted by: Reverse Date, Date, Thread, Author

Re: [PATCH] Reorder the documentation of typeset flags

Sorry for the delay answering this, I have been traveling.

I reverted this to plain text mode because something about the HTML
format was preventing certain bits from being deleted.  (It's been
usual practice on zsh-workers to use plain text.)

On Tue, Aug 25, 2026 at 2:59 PM Philippe Altherr
<philippe.altherr@xxxxxxxxx> wrote:
>
> Below is an updated version, see the second commit on GitHib to view the additional changes.
>
> Any reason why we don't allow -t for named references? I don't see any incompatibility.

There's no incompatibility now.  It used to conflict with the use of
tags for loop detection.

On the other hand tagging itself is a strange and little-used feature.

> I have added a sentence at the beginning to explain that -n, -T, and -f change the set of valid additional flags and their meaning.

Great.  A couple of nits:

1) When writing a code example (i.e. more than a single word) inside
tt(), the convention is to also place scare quotes around the outside,
e.g., `tt(typeset -f)'

2) Use of two clauses beginning with "but" in this sentence is awkward:

+The var(name) so created may not be an array element nor use
+a subscript, but the var(value) assigned may be any valid parameter
+name, but not a subscripted array (or associative array) element nor
+an array slice.

Perhaps
 a subscript, but the var(value) assigned may be any valid parameter
 name with the exception of subscripted array (or associative array)
 elements and array slices.
Messages sorted by: Reverse Date, Date, Thread, Author