From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: zsh-users@zsh.org
Subject: Re: Problem with user function
Date: Fri, 23 Feb 2024 20:40:19 +0100 [thread overview]
Message-ID: <CAN=4vMrBRocs3ReOJVE0LSu2upqPyZa_D02c0J=CM=Z+zZPQeg@mail.gmail.com> (raw)
In-Reply-To: <c363ce8d-97a1-48ff-93db-035bf7bfcd01@eastlink.ca>
On Fri, Feb 23, 2024 at 8:26 PM Ray Andrews <rayandrews@eastlink.ca> wrote:
>
> This is basically a dead issue now, but trying it is exactly what I did:
>
>
> % alias X='echo howdy'; Y() { X }
> zsh: defining function based on alias `Y'
> zsh: parse error near `()'
Can you reproduce this by running the command within `zsh -f`? Recall
that `zsh -f` gives you a blank state: zsh with no rc files sourced.
> BTW, interesting that his problem was solved by adding 'function' -- I though that was always optional, but in this case the parser seems to care.
Non-global aliases are expanded only in command position, so adding
`function` in front of `ls()` disables alias expansion of `ls` and
thus fixes the problem Duke was having.
Roman.
next prev parent reply other threads:[~2024-02-23 19:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 17:49 Duke Normandin
2024-02-23 18:16 ` Ray Andrews
2024-02-23 18:31 ` Roman Perepelitsa
2024-02-23 18:36 ` Bart Schaefer
2024-02-23 19:26 ` Ray Andrews
2024-02-23 19:40 ` Roman Perepelitsa [this message]
2024-02-23 19:59 ` Ray Andrews
2024-02-23 20:05 ` Roman Perepelitsa
2024-02-23 20:27 ` Bart Schaefer
2024-02-23 20:34 ` Bart Schaefer
2024-02-23 20:46 ` Ray Andrews
2024-02-23 18:32 ` Bart Schaefer
2024-02-23 18:52 ` Ray Andrews
2024-02-23 18:30 ` Roman Perepelitsa
2024-02-23 18:35 ` Duke Normandin
2024-02-23 18:50 ` Duke Normandin
2024-02-23 18:52 ` Roman Perepelitsa
2024-02-23 18:56 ` Duke Normandin
2024-02-23 19:00 ` Roman Perepelitsa
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='CAN=4vMrBRocs3ReOJVE0LSu2upqPyZa_D02c0J=CM=Z+zZPQeg@mail.gmail.com' \
--to=roman.perepelitsa@gmail.com \
--cc=rayandrews@eastlink.ca \
--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).