From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-workers@zsh.org
Subject: Re: Defining function based on alias
Date: Mon, 09 Jan 2017 10:33:40 +0000 [thread overview]
Message-ID: <20170109103340.01f045cf@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <20170109040258.GA8019@fujitsu.shahaf.local2>
On Mon, 9 Jan 2017 04:02:58 +0000
Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> Should these two behave differently when the new option is set? The
> first case appeared to be a non-anonymous function definition and the
> second a multifuncdef, but the alias changed the semantics.
I wasn't proposing to try to protect everyone from every possible error,
just the case we know is quite common even in normal use of functions
and aliases.
Conversely, if you need to do clever tricks I'm assuming you will simply
sign on the dotted line to say you will take responsibility and set the
option.
I do need to add something to the README.
pws
next prev parent reply other threads:[~2017-01-09 10:33 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
2017-01-09 4:02 ` Daniel Shahaf
2017-01-09 10:33 ` Peter Stephenson [this message]
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=20170109103340.01f045cf@pwslap01u.europe.root.pri \
--to=p.stephenson@samsung.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).