Accidental function definition - bug or feature?

Accidental function definition - bug or feature?

[Holger Hoffstätte]

Hi,

today I accidentally b0rked my shell with git and an unquoted filename via
copypasta. To reproduce:

$git add foo().bar
$git --version    
git:7: command not found: .bar

Turns out this unhelpfully defined a local function, which now shadows
the command:

$functions git
git () {
	.bar
}

Obviously everything works correctly with quoted filenames.
Also bash complains as I would have expected:

bash$ git add foo().bar
bash: syntax error near unexpected token `('

So..bug or feature?

thanks,
Holger

Re: Accidental function definition - bug or feature?

[Eric Cook]

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.

Re: Accidental function definition - bug or feature?

[ZyX]

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

Re: Accidental function definition - bug or feature?

[Clint Hepner]

> 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