From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: Problem with user function
Date: Fri, 23 Feb 2024 10:52:18 -0800 [thread overview]
Message-ID: <9bde9702-d7cb-4f18-bb44-dd816260b5d5@eastlink.ca> (raw)
In-Reply-To: <CAH+w=7ZmFB79PKepHtT6T_2RVnxzKEcaRqECHaaLL7++N5-XFA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 695 bytes --]
On 2024-02-23 10:32, Bart Schaefer wrote:
> Close, Ray, but not quite.
>
> That message means that the thing on the LEFT side of the empty parens
> () refers to an alias, not that something inside the function does.
I knew you guys would correct any errors, I was just taking a first stab
at it.
And that one means that whatever the alias expanded into, was not a
> syntactically valid function name, so it can't have () after it.
Right!
> That part you got right. Generally speaking any inquiry that begins
> with "After installing .oh-my-zsh," should be directed to an oh-my-zsh
> forum before coming here.
Let's be kind to the Prodigal Sons, returning from the fleshpots of
oh-my-zsh.
[-- Attachment #2: Type: text/html, Size: 1560 bytes --]
next prev parent reply other threads:[~2024-02-23 18:53 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
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 [this message]
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=9bde9702-d7cb-4f18-bb44-dd816260b5d5@eastlink.ca \
--to=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).