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.