From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Defining function based on alias
Date: Sun, 8 Jan 2017 16:09:21 -0800 [thread overview]
Message-ID: <170108160921.ZM11340@torch.brasslantern.com> (raw)
In-Reply-To: <20170108191922.3d3de59f@ntlworld.com>
On Jan 8, 7:19pm, Peter Stephenson wrote:
}
} I am about to commit the following, which I hope will hope will stop
} people coming to grief with this common confusion. Please say if you
} see any problems.
OK, here's an unusual case ...
alias safely:foo='[[ -n $functions[foo] ]] || foo'
safely:foo() { echo this is foo only if no other foo }
I hesitate to suggest further convolutions, but maybe an option to the
alias command to "locally" switch on ALIAS_FUNC_DEF if it's actually
*meant* to be used that way?
Probably not very important.
next prev parent reply other threads:[~2017-01-09 3:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-07 22:16 Peter Stephenson
2017-01-08 19:19 ` Peter Stephenson
2017-01-08 20:14 ` Bart Schaefer
2017-01-08 20:23 ` Peter Stephenson
2017-01-09 0:09 ` Bart Schaefer [this message]
2017-01-09 4:02 ` Daniel Shahaf
2017-01-09 10:33 ` Peter Stephenson
2017-01-09 1:55 ` Daniel Shahaf
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=170108160921.ZM11340@torch.brasslantern.com \
--to=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).