From: Perry Smith <pedz@easesoftware.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: zsh-users@zsh.org
Subject: Re: Alias call in function fails...
Date: Tue, 23 Jun 2020 07:46:50 -0500 [thread overview]
Message-ID: <D8EC8611-5960-4FFC-9D91-367BEAF77859@easesoftware.com> (raw)
In-Reply-To: <20200623120429.2c889b67@tarpaulin.shahaf.local2>
> On Jun 23, 2020, at 7:04 AM, Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
>
> Andreas Kusalananda Kähäri wrote on Tue, 23 Jun 2020 13:28 +0200:
>> On Tue, Jun 23, 2020 at 11:55:20AM +0200, Mikael Magnusson wrote:
>>> On 6/23/20, Andreas Kusalananda Kähäri <andreas.kahari@abc.se> wrote:
>>>> On Tue, Jun 23, 2020 at 01:23:55AM +0200, Mikael Magnusson wrote:
>>>>> Aliases are expanded on parse time, which means aliases defined in a
>>>>> file won't be usable in that same file. (Because it is parsed in its
>>>>> entirety before any of the code is actually run).
>>>>
>>>> If the alias is defined before the definition of the function, it ought to
>>>> work.
>>>
>>> As I already explained, it will not.
>>>
>>
>> As Peter Stephenson explained, it depends.
>>
>
> See also the ALIAS_FUNC_DEF option.
My amateur 2 cents … I gave up on aliases with bash and never tried them with zsh.
Aliases are just weird oddities that have lots of special cases. Since functions now exist (aliases came first in the global history of shells), I don’t see any advantages to aliases and they have many problems.
I don’t know of anything an alias can do that a function can’t?
next prev parent reply other threads:[~2020-06-23 12:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 12:49 Frank Gallacher
2020-06-22 23:23 ` Mikael Magnusson
2020-06-23 8:37 ` Andreas Kusalananda Kähäri
2020-06-23 9:14 ` Peter Stephenson
2020-06-23 9:55 ` Mikael Magnusson
2020-06-23 11:28 ` Andreas Kusalananda Kähäri
2020-06-23 12:04 ` Daniel Shahaf
2020-06-23 12:46 ` Perry Smith [this message]
2020-06-23 13:10 ` Kamil Dudka
2020-06-23 16:03 ` Bart Schaefer
2020-06-23 21:14 ` Perry Smith
2020-06-23 22:54 ` Daniel Shahaf
2020-06-23 23:29 ` Perry Smith
2020-06-23 23:43 ` Bart Schaefer
2020-06-24 0:47 ` Perry Smith
2020-06-24 9:28 ` Daniel Shahaf
2020-06-24 12:55 ` Perry Smith
2020-06-23 23:40 ` Bart Schaefer
2020-06-24 10:10 ` Daniel Shahaf
2020-06-24 10:47 ` Daniel Shahaf
2020-06-24 2:58 ` Grant Taylor
2020-06-29 16:24 ` Sebastian Gniazdowski
2020-06-29 16:55 ` Bart Schaefer
2020-06-30 4:02 ` Bart Schaefer
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=D8EC8611-5960-4FFC-9D91-367BEAF77859@easesoftware.com \
--to=pedz@easesoftware.com \
--cc=d.s@daniel.shahaf.name \
--cc=zsh-users@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).