zsh-workers
 help / color / mirror / code / Atom feed
* How to fix run-help-* functions?
@ 2023-03-07 14:30 Michele Venturi
  2023-03-07 17:13 ` Philippe Troin
  2023-03-07 17:22 ` Bart Schaefer
  0 siblings, 2 replies; 15+ messages in thread
From: Michele Venturi @ 2023-03-07 14:30 UTC (permalink / raw)
  To: zsh-workers

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

Just try "autoload run-help-sudo; run-help sudo" or "autoload run-help-git;
run-help git" etc. to see the error.
<https://about.me/dardo82?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=gmail_api&utm_content=thumb>
Michele Venturi
about.me/dardo82
<https://about.me/dardo82?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=gmail_api&utm_content=thumb>

[-- Attachment #2: Type: text/html, Size: 1823 bytes --]

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

* Re: How to fix run-help-* functions?
  2023-03-07 14:30 How to fix run-help-* functions? Michele Venturi
@ 2023-03-07 17:13 ` Philippe Troin
  2023-03-13 11:09   ` Michele Venturi
  2023-03-07 17:22 ` Bart Schaefer
  1 sibling, 1 reply; 15+ messages in thread
From: Philippe Troin @ 2023-03-07 17:13 UTC (permalink / raw)
  To: Michele Venturi, zsh-workers

On Tue, 2023-03-07 at 15:30 +0100, Michele Venturi wrote:
> Just try "autoload run-help-sudo; run-help sudo" or "autoload run-
> help-git; run-help git" etc. to see the error.

What's wrong with run-help?

   % zsh -f
   % echo $ZSH_VERSION                    
   5.8.1
   % export PAGER='head -n 5'
   % autoload run-help-git; run-help git
   GIT(1)                            Git Manual                            GIT(1)
   
   NAME
          git - the stupid content tracker
   
   % autoload run-help-sudo; run-help sudo
   SUDO(8)                   BSD System Manager's Manual                  SUDO(8)
   
   NAME
        sudo, sudoedit — execute a command as another user
   
   % 

Phil.


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

* Re: How to fix run-help-* functions?
  2023-03-07 14:30 How to fix run-help-* functions? Michele Venturi
  2023-03-07 17:13 ` Philippe Troin
@ 2023-03-07 17:22 ` Bart Schaefer
  2023-03-07 17:31   ` Peter Stephenson
  1 sibling, 1 reply; 15+ messages in thread
From: Bart Schaefer @ 2023-03-07 17:22 UTC (permalink / raw)
  To: Michele Venturi; +Cc: zsh-workers

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

On Tue, Mar 7, 2023 at 8:55 AM Michele Venturi <dardo82@gmail.com> wrote:

> Just try "autoload run-help-sudo; run-help sudo" or "autoload
> run-help-git; run-help git" etc. to see the error.
>

The run-help functions have to be passed through "make install", you can't
run them out of the zsh source tree.  Does that, ah, help?

[-- Attachment #2: Type: text/html, Size: 661 bytes --]

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

* Re: How to fix run-help-* functions?
  2023-03-07 17:22 ` Bart Schaefer
@ 2023-03-07 17:31   ` Peter Stephenson
  2023-03-07 17:40     ` Bart Schaefer
  0 siblings, 1 reply; 15+ messages in thread
From: Peter Stephenson @ 2023-03-07 17:31 UTC (permalink / raw)
  To: Michele Venturi, zsh-workers

> On 07/03/2023 17:22 Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Tue, Mar 7, 2023 at 8:55 AM Michele Venturi <dardo82@gmail.com> wrote:
> > Just try "autoload run-help-sudo; run-help sudo" or "autoload run-help-git; run-help git" etc. to see the error.
> 
> The run-help functions have to be passed through "make install", you can't run them out of the zsh source tree. Does that, ah, help?

The phrasing of the original question makes it hard to know how to
answer, but as another pointer, please read the description
of how the system is supposed to work at the top of the zshcontrib
manual (Accessing On-Line Help) and ask further questions based on that.

(That's already assuming you are using the system at all, not the
default "run-help", which is aliased to "man", see the zshzle manual
for that.)

BTW this sort of question ("I'm a confused user who doesn't know how
to get x to work") belongs in zsh-users unless you've determined
something about the system is broken.

pws


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

* Re: How to fix run-help-* functions?
  2023-03-07 17:31   ` Peter Stephenson
@ 2023-03-07 17:40     ` Bart Schaefer
  2023-03-07 18:34       ` Michele Venturi
  2023-03-13 11:14       ` Michele Venturi
  0 siblings, 2 replies; 15+ messages in thread
From: Bart Schaefer @ 2023-03-07 17:40 UTC (permalink / raw)
  To: Peter Stephenson; +Cc: Michele Venturi, zsh-workers

On Tue, Mar 7, 2023 at 9:32 AM Peter Stephenson
<p.w.stephenson@ntlworld.com> wrote:
>
> BTW this sort of question ("I'm a confused user who doesn't know how
> to get x to work") belongs in zsh-users unless you've determined
> something about the system is broken.

If you don't do the "make install" part, you get an error about a
"shift" count being wrong, which probably looks like a bug rather than
a usage problem.


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

* Re: How to fix run-help-* functions?
  2023-03-07 17:40     ` Bart Schaefer
@ 2023-03-07 18:34       ` Michele Venturi
  2023-03-08  0:03         ` Bart Schaefer
  2023-03-13 11:14       ` Michele Venturi
  1 sibling, 1 reply; 15+ messages in thread
From: Michele Venturi @ 2023-03-07 18:34 UTC (permalink / raw)
  To: Bart Schaefer; +Cc: Peter Stephenson, zsh-workers

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

In which directory should I run "make install"?

On Tue, Mar 7, 2023, 18:41 Bart Schaefer <schaefer@brasslantern.com> wrote:

> On Tue, Mar 7, 2023 at 9:32 AM Peter Stephenson
> <p.w.stephenson@ntlworld.com> wrote:
> >
> > BTW this sort of question ("I'm a confused user who doesn't know how
> > to get x to work") belongs in zsh-users unless you've determined
> > something about the system is broken.
>
> If you don't do the "make install" part, you get an error about a
> "shift" count being wrong, which probably looks like a bug rather than
> a usage problem.
>

[-- Attachment #2: Type: text/html, Size: 1021 bytes --]

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

* Re: How to fix run-help-* functions?
  2023-03-07 18:34       ` Michele Venturi
@ 2023-03-08  0:03         ` Bart Schaefer
  0 siblings, 0 replies; 15+ messages in thread
From: Bart Schaefer @ 2023-03-08  0:03 UTC (permalink / raw)
  To: Michele Venturi; +Cc: Peter Stephenson, zsh-workers

On Tue, Mar 7, 2023 at 10:35 AM Michele Venturi <dardo82@gmail.com> wrote:
>
> In which directory should I run "make install"?

The top level.  There's no provision for installing run-help apart
from everything else.  You can try

make install.fns

but that does install everything under Completion as well as
everything under Functions.


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

* Re: How to fix run-help-* functions?
  2023-03-07 17:13 ` Philippe Troin
@ 2023-03-13 11:09   ` Michele Venturi
  0 siblings, 0 replies; 15+ messages in thread
From: Michele Venturi @ 2023-03-13 11:09 UTC (permalink / raw)
  To: Philippe Troin; +Cc: zsh-workers

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

On Tue, Mar 7, 2023, 18:13 Philippe Troin <phil@fifi.org> wrote:

> On Tue, 2023-03-07 at 15:30 +0100, Michele Venturi wrote:
> > Just try "autoload run-help-sudo; run-help sudo" or "autoload run-
> > help-git; run-help git" etc. to see the error.
>
> What's wrong with run-help?
>
>    % zsh -f
>    % echo $ZSH_VERSION
>    5.8.1
>    % export PAGER='head -n 5'
>    % autoload run-help-git; run-help git
>    GIT(1)                            Git Manual
> GIT(1)
>
>    NAME
>           git - the stupid content tracker
>
>    % autoload run-help-sudo; run-help sudo
>    SUDO(8)                   BSD System Manager's Manual
> SUDO(8)
>
>    NAME
>         sudo, sudoedit — execute a command as another user
>
>    %
>
> Phil.
>

If you don't unalias run-help it runs man so it seems to
work, but doesn't use the function defined by the shell.

[-- Attachment #2: Type: text/html, Size: 1655 bytes --]

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

* Re: How to fix run-help-* functions?
  2023-03-07 17:40     ` Bart Schaefer
  2023-03-07 18:34       ` Michele Venturi
@ 2023-03-13 11:14       ` Michele Venturi
  2023-03-13 16:06         ` Bart Schaefer
  1 sibling, 1 reply; 15+ messages in thread
From: Michele Venturi @ 2023-03-13 11:14 UTC (permalink / raw)
  To: Bart Schaefer; +Cc: Peter Stephenson, zsh-workers

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

On Tue, Mar 7, 2023, 18:41 Bart Schaefer <schaefer@brasslantern.com> wrote:

> On Tue, Mar 7, 2023 at 9:32 AM Peter Stephenson
> <p.w.stephenson@ntlworld.com> wrote:
> >
> > BTW this sort of question ("I'm a confused user who doesn't know how
> > to get x to work") belongs in zsh-users unless you've determined
> > something about the system is broken.
>
> If you don't do the "make install" part, you get an error about a
> "shift" count being wrong, which probably looks like a bug rather than
> a usage problem.
>

I've tried this but it doesn't make any difference,
maybe because make install is to install files,
not to modify them? I don't get how it works.

[-- Attachment #2: Type: text/html, Size: 1412 bytes --]

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

* Re: How to fix run-help-* functions?
  2023-03-13 11:14       ` Michele Venturi
@ 2023-03-13 16:06         ` Bart Schaefer
  2023-03-13 18:19           ` Mikael Magnusson
  0 siblings, 1 reply; 15+ messages in thread
From: Bart Schaefer @ 2023-03-13 16:06 UTC (permalink / raw)
  To: Michele Venturi; +Cc: Peter Stephenson, zsh-workers

On Mon, Mar 13, 2023 at 4:14 AM Michele Venturi <dardo82@gmail.com> wrote:
>
> On Tue, Mar 7, 2023, 18:41 Bart Schaefer <schaefer@brasslantern.com> wrote:
>>
>> If you don't do the "make install" part, you get an error about a
>> "shift" count being wrong, which probably looks like a bug rather than
>> a usage problem.
>
> I've tried this but it doesn't make any difference,

When you "configure" or by passing an environment variable to "make"
you can specify a custom location for the help files.

Because run-help is a shell function, it doesn't have a "source file"
and an "object file" so the source itself contains a replacement
string @runhelpdir@ which is updated by the installfns.sh script
during "make install".  Yes, we could have put a "run-help.in" file
somewhere and processed that at a different build step to create
run-help, but that complicates installing the rest of the functions.

The help directory is populated by the Util/helpfiles script, which is
run by "make install" in the Doc subdirectory (but I do not recommend
attempting to run make in individual subdirectories rather than
letting the top-level Makefile drive it.)

However, all of that turns out to be necessary but secondary, because
the real problem is that you're using run-help wrong.

You're not intended to type out "run-help sudo" and hit enter, you're
intended to type "sudo" and then invoke the run-help ZLE widget
(normally ESC h or Alt+h), which then calls the run-help function with
some preliminary setup having been done.

Question for the audience is whether we want to consider this a bug
and make it possible to use run-help as a standalone function.


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

* Re: How to fix run-help-* functions?
  2023-03-13 16:06         ` Bart Schaefer
@ 2023-03-13 18:19           ` Mikael Magnusson
  2023-03-13 20:31             ` Bart Schaefer
  0 siblings, 1 reply; 15+ messages in thread
From: Mikael Magnusson @ 2023-03-13 18:19 UTC (permalink / raw)
  To: Bart Schaefer; +Cc: Michele Venturi, Peter Stephenson, zsh-workers

On 3/13/23, Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Mon, Mar 13, 2023 at 4:14 AM Michele Venturi <dardo82@gmail.com> wrote:
>>
>> On Tue, Mar 7, 2023, 18:41 Bart Schaefer <schaefer@brasslantern.com>
>> wrote:
>>>
>>> If you don't do the "make install" part, you get an error about a
>>> "shift" count being wrong, which probably looks like a bug rather than
>>> a usage problem.
>>
>> I've tried this but it doesn't make any difference,
>
> When you "configure" or by passing an environment variable to "make"
> you can specify a custom location for the help files.
>
> Because run-help is a shell function, it doesn't have a "source file"
> and an "object file" so the source itself contains a replacement
> string @runhelpdir@ which is updated by the installfns.sh script
> during "make install".  Yes, we could have put a "run-help.in" file
> somewhere and processed that at a different build step to create
> run-help, but that complicates installing the rest of the functions.
>
> The help directory is populated by the Util/helpfiles script, which is
> run by "make install" in the Doc subdirectory (but I do not recommend
> attempting to run make in individual subdirectories rather than
> letting the top-level Makefile drive it.)
>
> However, all of that turns out to be necessary but secondary, because
> the real problem is that you're using run-help wrong.
[moved this part to after]
> Question for the audience is whether we want to consider this a bug
> and make it possible to use run-help as a standalone function.

It could/should at least output some diagnostic, because it is very
easy for an end-user (or very confused developer) to do this:
% git<invoke run-help>
[git manpage is shown]
# above prompt has now changed to this:
% run-help git
% git<now press page up and enter which changes this line to:>
% run-help git
git is /usr/bin/git
run-help:shift:106: shift count must be <= $#


> You're not intended to type out "run-help sudo" and hit enter, you're
> intended to type "sudo" and then invoke the run-help ZLE widget
> (normally ESC h or Alt+h), which then calls the run-help function with
> some preliminary setup having been done.

Looking at the code for processcmd it seems to literally only insert
the string "run-help git" on the command line, so what exactly is this
preliminary setup? I can't find it. The comment for the function is:
/* Run '$WIDGET $commandword' and then restore the command-line using
push-line. */
which is missing some key piece of information.

-- 
Mikael Magnusson


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

* Re: How to fix run-help-* functions?
  2023-03-13 18:19           ` Mikael Magnusson
@ 2023-03-13 20:31             ` Bart Schaefer
  2023-03-13 20:41               ` Bart Schaefer
  0 siblings, 1 reply; 15+ messages in thread
From: Bart Schaefer @ 2023-03-13 20:31 UTC (permalink / raw)
  To: Mikael Magnusson; +Cc: Michele Venturi, Peter Stephenson, zsh-workers

On Mon, Mar 13, 2023 at 11:19 AM Mikael Magnusson <mikachu@gmail.com> wrote:
>
> On 3/13/23, Bart Schaefer <schaefer@brasslantern.com> wrote:
> > Question for the audience is whether we want to consider this a bug
> > and make it possible to use run-help as a standalone function.
>
> It could/should at least output some diagnostic, because it is very
> easy for an end-user (or very confused developer) to do this:
> % git<invoke run-help>
> % git<now press page up and enter which changes this line to:>
> % run-help git
> git is /usr/bin/git
> run-help:shift:106: shift count must be <= $#

A reasonable point.

> Looking at the code for processcmd it seems to literally only insert
> the string "run-help git" on the command line, so what exactly is this
> preliminary setup? I can't find it.

It does a push-line so that the run-help function can retrieve it with
getln.  See workers/49218

If there's no line pushed, the run-help function is going to push a
blank one (with print -z) immediately after getln fails, so there's
several things that need to (not) happen if the widget is not used.


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

* Re: How to fix run-help-* functions?
  2023-03-13 20:31             ` Bart Schaefer
@ 2023-03-13 20:41               ` Bart Schaefer
  2023-03-20 14:37                 ` Michele Venturi
  0 siblings, 1 reply; 15+ messages in thread
From: Bart Schaefer @ 2023-03-13 20:41 UTC (permalink / raw)
  To: Mikael Magnusson, Michele Venturi; +Cc: zsh-workers

On Mon, Mar 13, 2023 at 1:31 PM Bart Schaefer <schaefer@brasslantern.com> wrote:
>
> It does a push-line so that the run-help function can retrieve it with
> getln.  See workers/49218
>
> If there's no line pushed, the run-help function is going to push a
> blank one (with print -z) immediately after getln fails, so there's
> several things that need to (not) happen if the widget is not used.

This seems to cover it:

diff --git a/Functions/Misc/run-help b/Functions/Misc/run-help
index d52c1b032..0bf84447a 100644
--- a/Functions/Misc/run-help
+++ b/Functions/Misc/run-help
@@ -98,9 +98,9 @@ do
            if whence "run-help-$1:t" >/dev/null
            then
                local cmd_args
-               builtin getln cmd_args
+               builtin getln cmd_args &&
                builtin print -z "$cmd_args"
-               cmd_args=( ${(z)cmd_args} )
+               cmd_args=( ${(z)${cmd_args:-"$*"}} )

                 # Discard the command itself & everything before it.
                 shift $cmd_args[(i)${run_help_orig_cmd:-$1}] cmd_args ||


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

* Re: How to fix run-help-* functions?
  2023-03-13 20:41               ` Bart Schaefer
@ 2023-03-20 14:37                 ` Michele Venturi
  2023-03-21  1:05                   ` Bart Schaefer
  0 siblings, 1 reply; 15+ messages in thread
From: Michele Venturi @ 2023-03-20 14:37 UTC (permalink / raw)
  To: Bart Schaefer; +Cc: Mikael Magnusson, zsh-workers

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

On Mon, Mar 13, 2023, 21:41 Bart Schaefer <schaefer@brasslantern.com> wrote:

This seems to cover it:
>
> diff --git a/Functions/Misc/run-help b/Functions/Misc/run-help
> index d52c1b032..0bf84447a 100644
> --- a/Functions/Misc/run-help
> +++ b/Functions/Misc/run-help
> @@ -98,9 +98,9 @@ do
>             if whence "run-help-$1:t" >/dev/null
>             then
>                 local cmd_args
> -               builtin getln cmd_args
> +               builtin getln cmd_args &&
>                 builtin print -z "$cmd_args"
> -               cmd_args=( ${(z)cmd_args} )
> +               cmd_args=( ${(z)${cmd_args:-"$*"}} )
>
>                  # Discard the command itself & everything before it.
>                  shift $cmd_args[(i)${run_help_orig_cmd:-$1}] cmd_args ||
>

I hope that's enough context,I've an alias named "pkgu" set to "sudo pacman
-S -y -u" and "run-help pkgu" gives
the same error as before, can you check it on your end?

[-- Attachment #2: Type: text/html, Size: 1754 bytes --]

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

* Re: How to fix run-help-* functions?
  2023-03-20 14:37                 ` Michele Venturi
@ 2023-03-21  1:05                   ` Bart Schaefer
  0 siblings, 0 replies; 15+ messages in thread
From: Bart Schaefer @ 2023-03-21  1:05 UTC (permalink / raw)
  To: Michele Venturi; +Cc: Mikael Magnusson, zsh-workers

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

On Mon, Mar 20, 2023 at 7:37 AM Michele Venturi <dardo82@gmail.com> wrote:
>
> I hope that's enough context

Typically we'd like at least OS, zsh version, whether you built it
yourself or installed packaged binaries, and a copy-paste of text from
your terminal showing the command you ran and the resulting output
(edited to relevant portions if very long).

Also "functions -T run-help" (in this case) would produce xtrace
output of the function, which might help you investigate before asking
others to do so for you.

However, given we're already this far down a thread:

> I've an alias named "pkgu" set to "sudo pacman -S -y -u" and "run-help pkgu" gives
> the same error as before, can you check it on your end?

Besides not anticipating use outside widget context, some recent
changes to run-help also did not consider that aliases result in a
recursive call, or (at least) presumed that aliases would always
mention their own name somewhere in the expansion (e.g., alias
foo="sudo foo" or the like).  Same symptom, somewhat different cause.
Both stem from an attempt to optimize out a while-loop by using
${ary[(i)...]} which in turn didn't consider what happens when the (i)
search fails.

However, we're approaching a point of diminishing returns here.
Further attempts to make sense of the foregoing risk e.g. regressing
workers/31634.  It may be better to discard the error output from the
failed shift and get on with things.  After some memory-refreshment
with the mailing list archives of past changes, the problem comes down
to something like this:

Suppose we have an alias like g='git' and on the command line is "g
diff".  We'd like the run-help widget to first unpack "g" and then
analyze the full command line as "git diff" which ultimately invokes
"run-help-git diff" to finally produce the help for the git "diff"
subcommand.

So in widget context, run-help starts by looking up "g" as an alias
and makes a recursive call on "run-help git" -- which isn't good
enough, it's lost the argument "diff".  This is where getln/print -z
come in, the recursive call pulls up the original command line
(getln), discards the "g", and appends the remainder to get "git diff"
and off we go.  However, there are all sorts of complications -- what
if the alias is g='LANG=C sudo git' or some such?  Skipping arbitrary
prefix stuff to reach the "remainder" is what that "shift" is
attempting to do.

When run-help is invoked outside widget context, there's no source
line to search for the original command name.  My first pass at this
fell back on searching the arguments passed to run-help, but that
fails on the recursive call into the expansion of the alias because
the "original command" doesn't actually appear in the expansion.  It's
possible this would also fail in widget context if one alias itself
expanded to a second alias, etc.  And that doesn't even begin to get
into possible side-effects of "alias -g".

There are several other ways this can fail -- so the most reasonable
thing might be to give up if "skip the prefix" fails and treat the
command as too complex to generate help.

The attached (follows on to previous patch) might do a little better
than simply "give up", but it also might introduce some unwanted
differences.

[-- Attachment #2: rh_shift.txt --]
[-- Type: text/plain, Size: 1104 bytes --]

diff --git a/Functions/Misc/run-help b/Functions/Misc/run-help
index 14d09bd65..462044b72 100644
--- a/Functions/Misc/run-help
+++ b/Functions/Misc/run-help
@@ -58,11 +58,11 @@ do
     case $what in
     (*( is an alias for (noglob|nocorrect))*)
 	[[ ${what[(w)7]:t} != ${what[(w)1]} ]] &&
-	  run_help_orig_cmd=${what[(w)1]} run-help ${what[(w)7]:t}
+	  run_help_orig_cmd=${what[(w)1]} run-help ${what[(w)7]:t} ${(z)${what[(w)8,-1]}}
 	;;
     (*( is an alias)*)
 	[[ ${what[(w)6]:t} != ${what[(w)1]} ]] &&
-	  run_help_orig_cmd=${what[(w)1]} run-help ${what[(w)6]:t}
+	  run_help_orig_cmd=${what[(w)1]} run-help ${what[(w)6]:t} ${(z)${what[(w)7,-1]}}
 	;;
     (*( is a * function))
 	case ${what[(w)1]} in
@@ -103,7 +103,7 @@ do
 		cmd_args=( ${(z)${cmd_args:-"$*"}} )
 
                 # Discard the command itself & everything before it.
-                shift $cmd_args[(i)${run_help_orig_cmd:-$1}] cmd_args ||
+                shift $cmd_args[(i)(${run_help_orig_cmd}|$1)] cmd_args 2>/dev/null ||
                     continue
 
                 # Discard options, parameter assignments & paths.

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

end of thread, other threads:[~2023-03-21  1:06 UTC | newest]

Thread overview: 15+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-03-07 14:30 How to fix run-help-* functions? Michele Venturi
2023-03-07 17:13 ` Philippe Troin
2023-03-13 11:09   ` Michele Venturi
2023-03-07 17:22 ` Bart Schaefer
2023-03-07 17:31   ` Peter Stephenson
2023-03-07 17:40     ` Bart Schaefer
2023-03-07 18:34       ` Michele Venturi
2023-03-08  0:03         ` Bart Schaefer
2023-03-13 11:14       ` Michele Venturi
2023-03-13 16:06         ` Bart Schaefer
2023-03-13 18:19           ` Mikael Magnusson
2023-03-13 20:31             ` Bart Schaefer
2023-03-13 20:41               ` Bart Schaefer
2023-03-20 14:37                 ` Michele Venturi
2023-03-21  1:05                   ` Bart Schaefer

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).