zsh-workers
 help / color / mirror / code / Atom feed
From: "Jörg Sommer" <joerg@jo-so.de>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Oliver Kiddle <opk@zsh.org>, zsh-workers@zsh.org
Subject: Re: [PATCH v2] run-help for docker, perf, podman, ssh, svnadmin
Date: Sun, 24 Sep 2023 09:31:54 +0200	[thread overview]
Message-ID: <20230924073154.m2emhhu4fdaieflo@jo-so.de> (raw)
In-Reply-To: <CAH+w=7Y4AgU8ypJd6oJcXXd2uoJx67fffYmQA8STX84i5ecU+Q@mail.gmail.com>

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

Bart Schaefer schrieb am Sa 23. Sep, 10:57 (-0500):
> On Sat, Sep 23, 2023 at 2:17 AM Jörg Sommer <joerg@jo-so.de> wrote:
> >
> > Oliver Kiddle schrieb am Do 21. Sep, 00:41 (+0200):
> > > The other was 51746 which did elicit a couple of less than enthusiastic
> > > replies.
> >
> > I guess you talk about “run-help: Support variables in aliases”. This
> > discussion was entrenched and no solution was found.
> 
> Returning to that below ... meanwhile:
> 
> > I still have the
> > problem of
> >
> > ```
> > % unalias run-help
> > % autoload run-help
> > % alias tt1='LC_ALL=C true' tt2=true
> > % run-help tt2
> > tt2 is an alias for true
> > % run-help tt1
> > tt1 is an alias for LC_ALL=C true
> > LC_ALL=C not found
> > No manual entry for LC_ALL=C
> > ```
> 
> This works for me in the current dev version, that is, after
> workers/51593 is applied.

This would be sufficient for me, because I can substitute the variable
assignment in the alias definition.

> What continues not to work is your original example of an alias that
> invokes another alias, where the first alias is nothing but an assignment:
> 
> > zenbook% alias LCC='LC_ALL=C'; alias T='LCC true'
> > zenbook% run-help T
> > No manual entry for T
> > ```

The alias LCC I use mostly interactively and put it in all other alias
definitions only for convenience. But in the zshrc I can use a variable
which expands on definition.


Regards Jörg

-- 
chinesiches Sprichwort:
Wer fragt, ist ein Narr für fünf Minuten.
Wer nicht fragt, ist ein Narr fürs ganze Leben.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 269 bytes --]

  reply	other threads:[~2023-09-24  7:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-17 22:12 [PATCH 1/4] run-help: Support variables in aliases Jörg Sommer
2023-05-17 22:12 ` [PATCH 2/4] run-help-ip: Reduce the match for link to l Jörg Sommer
2023-05-17 22:12 ` [PATCH 3/4] run-help-openssl: Reduce the code Jörg Sommer
2023-05-17 22:12 ` [PATCH 4/4] run-help for docker, perf, podman, ssh, svnadmin Jörg Sommer
2023-05-31 17:45   ` [PATCH v2] " Jörg Sommer
2023-09-20 22:41     ` Oliver Kiddle
2023-09-23  7:16       ` Jörg Sommer
2023-09-23 15:57         ` Bart Schaefer
2023-09-24  7:31           ` Jörg Sommer [this message]
2023-05-17 22:45 ` [PATCH 1/4] run-help: Support variables in aliases Bart Schaefer
2023-05-18  6:52   ` Jörg Sommer
2023-05-18  9:02   ` Peter Stephenson
2023-05-23 16:25 ` [PATCH v2] run-help-openssl: Reduce code and use new manpages Jörg Sommer

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=20230924073154.m2emhhu4fdaieflo@jo-so.de \
    --to=joerg@jo-so.de \
    --cc=opk@zsh.org \
    --cc=schaefer@brasslantern.com \
    --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).