zsh-workers
 help / color / mirror / Atom feed
* [regression] %2K prompt expansion no longer works
@ 2020-08-30 11:13 Stephane Chazelas
  2020-08-30 13:17 ` Mikael Magnusson
  2020-10-24 14:21 ` Mikael Magnusson
  0 siblings, 2 replies; 9+ messages in thread
From: Stephane Chazelas @ 2020-08-30 11:13 UTC (permalink / raw)
  To: Zsh hackers list

$ print -rnP %2K | hd
00000000  1b 5b 34 30 6d                                    |.[40m|
00000005

%K{2} is fine:

$ print -rnP '%K{2}' | hd
00000000  1b 5b 34 32 6d                                    |.[42m|
00000005

Introduced by worker:30496
(https://www.zsh.org/mla/workers/2012/msg00421.html
8a9b141652a0e4157056dc21e36a64ac712a7ee7 git commit).

Oddly, the comment there:

> Well, nobody objected so here's a version with de-duplicated
> code. The previous patch broke %K, but it works now (passed 1
> for is_fg on both paths).

Actually describes the bug here. Looks like Mikael just missed a bit in that
fix.

Should be fixed with:


diff --git a/Src/prompt.c b/Src/prompt.c
index bc9734720..997327e18 100644
--- a/Src/prompt.c
+++ b/Src/prompt.c
@@ -258,7 +258,7 @@ parsecolorchar(zattr arg, int is_fg)
 		bv->fm--;
 	}
     } else
-	arg = match_colour(NULL, 1, arg);
+	arg = match_colour(NULL, is_fg, arg);
     return arg;
 }
 
Cheers,
Stephane


^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [regression] %2K prompt expansion no longer works
  2020-08-30 11:13 [regression] %2K prompt expansion no longer works Stephane Chazelas
@ 2020-08-30 13:17 ` Mikael Magnusson
  2020-10-24 14:21 ` Mikael Magnusson
  1 sibling, 0 replies; 9+ messages in thread
From: Mikael Magnusson @ 2020-08-30 13:17 UTC (permalink / raw)
  To: Zsh hackers list

On 8/30/20, Stephane Chazelas <stephane@chazelas.org> wrote:
> $ print -rnP %2K | hd
> 00000000  1b 5b 34 30 6d                                    |.[40m|
> 00000005
>
> %K{2} is fine:
>
> $ print -rnP '%K{2}' | hd
> 00000000  1b 5b 34 32 6d                                    |.[42m|
> 00000005
>
> Introduced by worker:30496
> (https://www.zsh.org/mla/workers/2012/msg00421.html
> 8a9b141652a0e4157056dc21e36a64ac712a7ee7 git commit).
>
> Oddly, the comment there:
>
>> Well, nobody objected so here's a version with de-duplicated
>> code. The previous patch broke %K, but it works now (passed 1
>> for is_fg on both paths).
>
> Actually describes the bug here. Looks like Mikael just missed a bit in
> that
> fix.

I likely only tested %K{2}, sorry about that (looks like not many
other people use %2K either though).

-- 
Mikael Magnusson


^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [regression] %2K prompt expansion no longer works
  2020-08-30 11:13 [regression] %2K prompt expansion no longer works Stephane Chazelas
  2020-08-30 13:17 ` Mikael Magnusson
@ 2020-10-24 14:21 ` Mikael Magnusson
  2020-10-25 20:12   ` Daniel Shahaf
  1 sibling, 1 reply; 9+ messages in thread
From: Mikael Magnusson @ 2020-10-24 14:21 UTC (permalink / raw)
  To: Zsh hackers list

On 8/30/20, Stephane Chazelas <stephane@chazelas.org> wrote:
> $ print -rnP %2K | hd
> 00000000  1b 5b 34 30 6d                                    |.[40m|
> 00000005
>
> %K{2} is fine:
>
> $ print -rnP '%K{2}' | hd
> 00000000  1b 5b 34 32 6d                                    |.[42m|
> 00000005
>
> Introduced by worker:30496
> (https://www.zsh.org/mla/workers/2012/msg00421.html
> 8a9b141652a0e4157056dc21e36a64ac712a7ee7 git commit).
>
> Oddly, the comment there:
>
>> Well, nobody objected so here's a version with de-duplicated
>> code. The previous patch broke %K, but it works now (passed 1
>> for is_fg on both paths).
>
> Actually describes the bug here. Looks like Mikael just missed a bit in
> that
> fix.
>
> Should be fixed with:
>
>
> diff --git a/Src/prompt.c b/Src/prompt.c
> index bc9734720..997327e18 100644
> --- a/Src/prompt.c
> +++ b/Src/prompt.c
> @@ -258,7 +258,7 @@ parsecolorchar(zattr arg, int is_fg)
>  		bv->fm--;
>  	}
>      } else
> -	arg = match_colour(NULL, 1, arg);
> +	arg = match_colour(NULL, is_fg, arg);
>      return arg;
>  }

Just noticed that these [unposted] testcases don't pass. Added some
debugging prints and it turns out that %F{green} uses a different code
than specifying the number. Eg,

    echo $F1 $F2 $F3 $F4 | cat -v

results in

^[[38;5;2m ^[[38;5;2m ^[[38;5;2m ^[[32m

(the results are equivalent if you explicitly set fg_start_code to
^[[38;5;, but the test case doesn't do that, and of course that might
not be what terminfo contains anyway.)

I think the correct fix is to not include F4 and K4 since they use
these definitions in the source code:
#define TC_COL_FG_START	"\033[3"
#define TC_COL_BG_START	"\033[4"

which will not match the others.

-- 
Mikael Magnusson


^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [regression] %2K prompt expansion no longer works
  2020-10-24 14:21 ` Mikael Magnusson
@ 2020-10-25 20:12   ` Daniel Shahaf
  2020-10-25 21:29     ` Mikael Magnusson
  0 siblings, 1 reply; 9+ messages in thread
From: Daniel Shahaf @ 2020-10-25 20:12 UTC (permalink / raw)
  To: Mikael Magnusson; +Cc: Zsh hackers list

Mikael Magnusson wrote on Sat, 24 Oct 2020 16:21 +0200:
> On 8/30/20, Stephane Chazelas <stephane@chazelas.org> wrote:
> > $ print -rnP %2K | hd
> > 00000000  1b 5b 34 30 6d                                    |.[40m|
> > 00000005
> >  
> > %K{2} is fine:  
> >
> > $ print -rnP '%K{2}' | hd
> > 00000000  1b 5b 34 32 6d                                    |.[42m|
> > 00000005
> >
> > Introduced by worker:30496
> > (https://www.zsh.org/mla/workers/2012/msg00421.html
> > 8a9b141652a0e4157056dc21e36a64ac712a7ee7 git commit).
> >
> > Oddly, the comment there:
> >  
> >> Well, nobody objected so here's a version with de-duplicated
> >> code. The previous patch broke %K, but it works now (passed 1
> >> for is_fg on both paths).  
> >
> > Actually describes the bug here. Looks like Mikael just missed a bit in
> > that
> > fix.
> >
> > Should be fixed with:
> >
> >
> > diff --git a/Src/prompt.c b/Src/prompt.c
> > index bc9734720..997327e18 100644
> > --- a/Src/prompt.c
> > +++ b/Src/prompt.c
> > @@ -258,7 +258,7 @@ parsecolorchar(zattr arg, int is_fg)
> >  		bv->fm--;  
> >  	}
> >      } else  
> > -	arg = match_colour(NULL, 1, arg);
> > +	arg = match_colour(NULL, is_fg, arg);
> >      return arg;  
> >  }  
> 
> Just noticed that these [unposted] testcases don't pass. Added some
> debugging prints and it turns out that %F{green} uses a different code
> than specifying the number. Eg,
> 
>     echo $F1 $F2 $F3 $F4 | cat -v
> 
> results in
> 
> ^[[38;5;2m ^[[38;5;2m ^[[38;5;2m ^[[32m
> 

Isn't this what Oliver just pointed out in another thread? —

Oliver Kiddle wrote in 47491:
> Regarding (1), I just noticed that a new D01prompt test case is failing
> on FreeBSD because ${(%):-%F{2}} is not producing the same as
> ${(%):-%F{green}}. This is a new test added just last month in 47352.
> 
> This is down to TXT_ATTR_FG_TERMCAP being set for 2 but not for green.


^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [regression] %2K prompt expansion no longer works
  2020-10-25 20:12   ` Daniel Shahaf
@ 2020-10-25 21:29     ` Mikael Magnusson
  2020-10-26  7:29       ` Stephane Chazelas
  0 siblings, 1 reply; 9+ messages in thread
From: Mikael Magnusson @ 2020-10-25 21:29 UTC (permalink / raw)
  To: Daniel Shahaf; +Cc: Zsh hackers list

On 10/25/20, Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> Mikael Magnusson wrote on Sat, 24 Oct 2020 16:21 +0200:
>> On 8/30/20, Stephane Chazelas <stephane@chazelas.org> wrote:
>> > $ print -rnP %2K | hd
>> > 00000000  1b 5b 34 30 6d                                    |.[40m|
>> > 00000005
>> >
>> > %K{2} is fine:
>> >
>> > $ print -rnP '%K{2}' | hd
>> > 00000000  1b 5b 34 32 6d                                    |.[42m|
>> > 00000005
>> >
>> > Introduced by worker:30496
>> > (https://www.zsh.org/mla/workers/2012/msg00421.html
>> > 8a9b141652a0e4157056dc21e36a64ac712a7ee7 git commit).
>> >
>> > Oddly, the comment there:
>> >
>> >> Well, nobody objected so here's a version with de-duplicated
>> >> code. The previous patch broke %K, but it works now (passed 1
>> >> for is_fg on both paths).
>> >
>> > Actually describes the bug here. Looks like Mikael just missed a bit in
>> > that
>> > fix.
>> >
>> > Should be fixed with:
>> >
>> >
>> > diff --git a/Src/prompt.c b/Src/prompt.c
>> > index bc9734720..997327e18 100644
>> > --- a/Src/prompt.c
>> > +++ b/Src/prompt.c
>> > @@ -258,7 +258,7 @@ parsecolorchar(zattr arg, int is_fg)
>> >  		bv->fm--;
>> >  	}
>> >      } else
>> > -	arg = match_colour(NULL, 1, arg);
>> > +	arg = match_colour(NULL, is_fg, arg);
>> >      return arg;
>> >  }
>>
>> Just noticed that these [unposted] testcases don't pass. Added some
>> debugging prints and it turns out that %F{green} uses a different code
>> than specifying the number. Eg,
>>
>>     echo $F1 $F2 $F3 $F4 | cat -v
>>
>> results in
>>
>> ^[[38;5;2m ^[[38;5;2m ^[[38;5;2m ^[[32m
>>
>
> Isn't this what Oliver just pointed out in another thread? —
>
> Oliver Kiddle wrote in 47491:
>> Regarding (1), I just noticed that a new D01prompt test case is failing
>> on FreeBSD because ${(%):-%F{2}} is not producing the same as
>> ${(%):-%F{green}}. This is a new test added just last month in 47352.
>>
>> This is down to TXT_ATTR_FG_TERMCAP being set for 2 but not for green.

It is, I'm not reading that thread though :).

-- 
Mikael Magnusson


^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [regression] %2K prompt expansion no longer works
  2020-10-25 21:29     ` Mikael Magnusson
@ 2020-10-26  7:29       ` Stephane Chazelas
  2020-10-29 23:09         ` Oliver Kiddle
  0 siblings, 1 reply; 9+ messages in thread
From: Stephane Chazelas @ 2020-10-26  7:29 UTC (permalink / raw)
  To: Mikael Magnusson; +Cc: Daniel Shahaf, Zsh hackers list

2020-10-25 22:29:44 +0100, Mikael Magnusson:
[...]
> >> Just noticed that these [unposted] testcases don't pass. Added some
> >> debugging prints and it turns out that %F{green} uses a different code
> >> than specifying the number. Eg,
> >>
> >>     echo $F1 $F2 $F3 $F4 | cat -v
> >>
> >> results in
> >>
> >> ^[[38;5;2m ^[[38;5;2m ^[[38;5;2m ^[[32m
[...]

I can reproduce with:

$ TERM=rxvt-unicode-256color zsh -c 'print -P %F{green}' | hd
00000000  1b 5b 33 32 6d 0a                                 |.[32m.|
00000006
$ TERM=rxvt-unicode-256color zsh -c 'print -P %F{1}' | hd
00000000  1b 5b 33 38 3b 35 3b 31  6d 0a                    |.[38;5;1m.|
0000000a

Shouldn't %F{green} give the same as %F{2} (echoti setaf 2) instead of
hardcoding the escape sequence?

-- 
Stephane


^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [regression] %2K prompt expansion no longer works
  2020-10-26  7:29       ` Stephane Chazelas
@ 2020-10-29 23:09         ` Oliver Kiddle
  2020-10-30  0:42           ` Bart Schaefer
  0 siblings, 1 reply; 9+ messages in thread
From: Oliver Kiddle @ 2020-10-29 23:09 UTC (permalink / raw)
  To: Mikael Magnusson, Daniel Shahaf, Zsh hackers list

On 26 Oct, Stephane Chazelas wrote:
> > >> Just noticed that these [unposted] testcases don't pass. Added some
> > >> debugging prints and it turns out that %F{green} uses a different code
> > >> than specifying the number. Eg,

> I can reproduce with:

> $ TERM=rxvt-unicode-256color zsh -c 'print -P %F{green}' | hd

> $ TERM=rxvt-unicode-256color zsh -c 'print -P %F{1}' | hd

> Shouldn't %F{green} give the same as %F{2} (echoti setaf 2) instead of
> hardcoding the escape sequence?

That's what I would have thought too. But then why has code been written
to avoid termcap in the case of named colours?

If nobody can remember, removing it may be the only way to find out. The
following patch would do that.

From my testing, the one arguable regression due to this is that when
assigning to region_highlight, we now lose the information of whether a
colour was specified in named or numbered form so fg=2 gets converted to
fg=green. Conversion to a canonical form seems harmless enough, or? And
if we only want to preserve the input form then the flag and associated
variables should be named differently.

This corresponds to possibility (1) from workers/47491. It'd be useful
to have opinions on this. Especially as this is removing rather than
adding code.

Oliver

diff --git a/Src/prompt.c b/Src/prompt.c
index 997327e18..6943eabc3 100644
--- a/Src/prompt.c
+++ b/Src/prompt.c
@@ -1696,28 +1696,11 @@ match_colour(const char **teststrp, int is_fg, int colour)
 		return TXT_ERROR;
 	}
     }
-    /*
-     * Try termcap for numbered characters if possible.
-     * Don't for named characters, since our best bet
-     * of getting the names right is with ANSI sequences.
-     */
-    if (!named && tccan(tc)) {
-	if (tccolours >= 0 && colour >= tccolours) {
-	    /*
-	     * Out of range of termcap colours.
-	     * Can we assume ANSI colours work?
-	     */
-	    if (colour > 7)
-		return TXT_ERROR; /* No. */
-	} else {
-	    /*
-	     * We can handle termcap colours and the number
-	     * is in range, so use termcap.
-	     */
-	    on |= is_fg ? TXT_ATTR_FG_TERMCAP :
-		TXT_ATTR_BG_TERMCAP;
-	}
-    }
+
+    /* Out of range of termcap colours and basic ANSI set. */
+    if (tccan(tc) && colour > 7 && colour >= tccolours)
+	return TXT_ERROR;
+
     return on | (zattr)colour << shft;
 }
 
@@ -1781,7 +1764,7 @@ match_highlight(const char *teststr, zattr *on_var)
  */
 
 static int
-output_colour(int colour, int fg_bg, int use_tc, int truecol, char *buf)
+output_colour(int colour, int fg_bg, int truecol, char *buf)
 {
     int atrlen = 3, len;
     char *ptr = buf;
@@ -1799,7 +1782,7 @@ output_colour(int colour, int fg_bg, int use_tc, int truecol, char *buf)
      * used instead of termcap even for colour > 7. Here this just emits the
      * color number, so it works fine for both zle_highlight and tercap cases
      */
-    } else if (use_tc || colour > 7) {
+    } else if (colour > 7) {
 	char digbuf[DIGBUFSIZE];
 	sprintf(digbuf, "%d", colour);
 	len = strlen(digbuf);
@@ -1836,7 +1819,6 @@ output_highlight(zattr atr, char *buf)
     if (atr & TXTFGCOLOUR) {
 	len = output_colour(txtchangeget(atr, TXT_ATTR_FG_COL),
 			    COL_SEQ_FG,
-			    (atr & TXT_ATTR_FG_TERMCAP),
 			    (atr & TXT_ATTR_FG_24BIT),
 			    ptr);
 	atrlen += len;
@@ -1853,7 +1835,6 @@ output_highlight(zattr atr, char *buf)
 	}
 	len = output_colour(txtchangeget(atr, TXT_ATTR_BG_COL),
 			    COL_SEQ_BG,
-			    (atr & TXT_ATTR_BG_TERMCAP),
 			    (atr & TXT_ATTR_BG_24BIT),
 			    ptr);
 	atrlen += len;
@@ -2018,7 +1999,6 @@ free_colour_buffer(void)
  * fg_bg indicates if we're changing the foreground or background.
  * tc indicates the termcap code to use, if appropriate.
  * def indicates if we're resetting the default colour.
- * use_termcap indicates if we should use termcap to output colours.
  * flags is either 0 or TSC_PROMPT.
  */
 
@@ -2028,7 +2008,7 @@ set_colour_attribute(zattr atr, int fg_bg, int flags)
 {
     char *ptr;
     int do_free, is_prompt = (flags & TSC_PROMPT) ? 1 : 0;
-    int colour, tc, def, use_termcap, use_truecolor;
+    int colour, tc, def, use_truecolor;
     int is_default_zle_highlight = 1;
 
     if (fg_bg == COL_SEQ_FG) {
@@ -2036,13 +2016,11 @@ set_colour_attribute(zattr atr, int fg_bg, int flags)
 	tc = TCFGCOLOUR;
 	def = txtchangeisset(atr, TXTNOFGCOLOUR);
 	use_truecolor = txtchangeisset(atr, TXT_ATTR_FG_24BIT);
-	use_termcap = txtchangeisset(atr, TXT_ATTR_FG_TERMCAP);
     } else {
 	colour = txtchangeget(atr, TXT_ATTR_BG_COL);
 	tc = TCBGCOLOUR;
 	def = txtchangeisset(atr, TXTNOBGCOLOUR);
 	use_truecolor = txtchangeisset(atr, TXT_ATTR_BG_24BIT);
-	use_termcap = txtchangeisset(atr, TXT_ATTR_BG_TERMCAP);
     }
 
     /* Test if current zle_highlight settings are customized, or
@@ -2057,17 +2035,14 @@ set_colour_attribute(zattr atr, int fg_bg, int flags)
     }
 
     /*
-     * If we're not restoring the default, and either have a
-     * colour value that is too large for ANSI, or have been told
-     * to use the termcap sequence, try to use the termcap sequence.
-     * True color is not covered by termcap.
+     * If we're not restoring the default or applying true color,
+     * try to use the termcap sequence.
      *
      * We have already sanitised the values we allow from the
      * highlighting variables, so much of this shouldn't be
      * necessary at this point, but we might as well be safe.
      */
-    if (!def && !use_truecolor &&
-	(is_default_zle_highlight && (colour > 7 || use_termcap)))
+    if (!def && !use_truecolor && is_default_zle_highlight)
     {
 	/*
 	 * We can if it's available, and either we couldn't get
diff --git a/Src/zsh.h b/Src/zsh.h
index 6cf1b4186..a26b2d05b 100644
--- a/Src/zsh.h
+++ b/Src/zsh.h
@@ -2726,11 +2726,6 @@ struct ttyinfo {
 /* Bits to shift the background colour */
 #define TXT_ATTR_BG_COL_SHIFT    (40)
 
-/* Flag to use termcap AF sequence to set colour, if available */
-#define TXT_ATTR_FG_TERMCAP      0x1000
-/* Flag to use termcap AB sequence to set colour, if available */
-#define TXT_ATTR_BG_TERMCAP      0x2000
-
 /* Flag to indicate that foreground is a 24-bit colour */
 #define TXT_ATTR_FG_24BIT        0x4000
 /* Flag to indicate that background is a 24-bit colour */
@@ -2739,16 +2734,15 @@ struct ttyinfo {
 /* Things to turn on, including values for the colour elements */
 #define TXT_ATTR_ON_VALUES_MASK	\
     (TXT_ATTR_ON_MASK|TXT_ATTR_FG_COL_MASK|TXT_ATTR_BG_COL_MASK|\
-     TXT_ATTR_FG_TERMCAP|TXT_ATTR_BG_TERMCAP|\
      TXT_ATTR_FG_24BIT|TXT_ATTR_BG_24BIT)
 
 /* Mask out everything to do with setting a foreground colour */
 #define TXT_ATTR_FG_ON_MASK \
-    (TXTFGCOLOUR|TXT_ATTR_FG_COL_MASK|TXT_ATTR_FG_TERMCAP|TXT_ATTR_FG_24BIT)
+    (TXTFGCOLOUR|TXT_ATTR_FG_COL_MASK|TXT_ATTR_FG_24BIT)
 
 /* Mask out everything to do with setting a background colour */
 #define TXT_ATTR_BG_ON_MASK \
-    (TXTBGCOLOUR|TXT_ATTR_BG_COL_MASK|TXT_ATTR_BG_TERMCAP|TXT_ATTR_BG_24BIT)
+    (TXTBGCOLOUR|TXT_ATTR_BG_COL_MASK|TXT_ATTR_BG_24BIT)
 
 /* Mask out everything to do with activating colours */
 #define TXT_ATTR_COLOUR_ON_MASK			\


^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [regression] %2K prompt expansion no longer works
  2020-10-29 23:09         ` Oliver Kiddle
@ 2020-10-30  0:42           ` Bart Schaefer
  2020-10-30  9:11             ` Peter Stephenson
  0 siblings, 1 reply; 9+ messages in thread
From: Bart Schaefer @ 2020-10-30  0:42 UTC (permalink / raw)
  To: Zsh hackers list

On Thu, Oct 29, 2020 at 4:09 PM Oliver Kiddle <opk@zsh.org> wrote:
>
> > Shouldn't %F{green} give the same as %F{2} (echoti setaf 2) instead of
> > hardcoding the escape sequence?
>
> That's what I would have thought too. But then why has code been written
> to avoid termcap in the case of named colours?
>
> If nobody can remember, removing it may be the only way to find out.

%F hasn't been around that long (comparatively, ahem) ... the git
history should provide some explanation.

https://www.zsh.org/mla/workers/2008/msg00647.html

Peter?  Jog anything?


^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [regression] %2K prompt expansion no longer works
  2020-10-30  0:42           ` Bart Schaefer
@ 2020-10-30  9:11             ` Peter Stephenson
  0 siblings, 0 replies; 9+ messages in thread
From: Peter Stephenson @ 2020-10-30  9:11 UTC (permalink / raw)
  To: Zsh hackers list

> On 30 October 2020 at 00:42 Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Thu, Oct 29, 2020 at 4:09 PM Oliver Kiddle <opk@zsh.org> wrote:
> >
> > > Shouldn't %F{green} give the same as %F{2} (echoti setaf 2) instead of
> > > hardcoding the escape sequence?
> >
> > That's what I would have thought too. But then why has code been written
> > to avoid termcap in the case of named colours?
> >
> > If nobody can remember, removing it may be the only way to find out.
> 
> %F hasn't been around that long (comparatively, ahem) ... the git
> history should provide some explanation.
> 
> https://www.zsh.org/mla/workers/2008/msg00647.html
> 
> Peter?  Jog anything?

I'm pretty sure this stuff was only ever done on the basis of "whatever
happened to work at the time".  The only master plan was to provide
as wide support as possible without making too many assumptions.
The assumptions to be made will correspondingly have changed over
the years.

pws


^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2020-10-30  9:12 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-08-30 11:13 [regression] %2K prompt expansion no longer works Stephane Chazelas
2020-08-30 13:17 ` Mikael Magnusson
2020-10-24 14:21 ` Mikael Magnusson
2020-10-25 20:12   ` Daniel Shahaf
2020-10-25 21:29     ` Mikael Magnusson
2020-10-26  7:29       ` Stephane Chazelas
2020-10-29 23:09         ` Oliver Kiddle
2020-10-30  0:42           ` Bart Schaefer
2020-10-30  9:11             ` Peter Stephenson

zsh-workers

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.vuxu.org/zsh-workers

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 zsh-workers zsh-workers/ http://inbox.vuxu.org/zsh-workers \
		zsh-workers@zsh.org
	public-inbox-index zsh-workers

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.vuxu.org/vuxu.archive.zsh.workers


code repositories for the project(s) associated with this inbox:

	https://git.vuxu.org/mirror/zsh/

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git