From: Clint Hepner <clint.hepner@gmail.com>
To: "zsh-users@zsh.org" <zsh-users@zsh.org>
Subject: Re: Accidental function definition - bug or feature?
Date: Tue, 27 Oct 2015 12:40:17 -0400 [thread overview]
Message-ID: <AB004151-5F5A-4954-966F-E0DF827BBE4C@gmail.com> (raw)
In-Reply-To: <3854791445530294@web16o.yandex.ru>
> On Oct 22, 2015, at 12:11 PM, ZyX <kp-pav@yandex.ru> wrote:
>
> 22.10.2015, 16:48, "Eric Cook" <llua@gmx.com>:
>>> On 10/22/2015 08:30 AM, Holger Hoffstätte wrote:
>>>
>>> So..bug or feature?
>>>
>>> thanks,
>>> Holger
>>
>> defining multiple functions at once is a feature
>>
>> mv cp() {
>> $0 -v "$@"
>> }
>>
>> or defining multiple TRAP functions to do the same thing are usual uses for it.
>
> Can be disabled with
>
> unsetopt multifuncdef
You can also undefine functions as an immediate fix:
unfunction git add foo
prev parent reply other threads:[~2015-10-27 16:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 12:30 Holger Hoffstätte
2015-10-22 13:47 ` Eric Cook
2015-10-22 16:11 ` ZyX
2015-10-27 16:40 ` Clint Hepner [this message]
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=AB004151-5F5A-4954-966F-E0DF827BBE4C@gmail.com \
--to=clint.hepner@gmail.com \
--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).