ZSH Shell support - Bug with a special character

ZSH Shell support - Bug with a special character

[Tobias]

Hi,

I'm just trying to run this script:
     git reset HEAD^
I'm using git to try to reset the code to a branch behind and zsh 
returns this message:
     zsh: no matches found: HEAD^

Thank you in advance,

Tobias Basteiro

Re: ZSH Shell support - Bug with a special character

[Peter Stephenson]

On Fri, 28 Feb 2014 14:00:46 -0300
Tobias <tobias.basteiro@openenglish.com> wrote:
> I'm just trying to run this script:
>      git reset HEAD^
> I'm using git to try to reset the code to a branch behind and zsh 
> returns this message:
>      zsh: no matches found: HEAD^

You have the EXTENDED_GLOB option set, in which ^ is a special
character.

If you don't need it, simply remove it from the start up file where it's
turned on or add "unsetopt EXTENDED_GLOB" after whatever code is setting
it.

If you do need EXTENDED_GLOB for other purposes but don't need that
particular syntax, and you have the latest version of zsh, you can turn
off that pattern character,

disable -p '^'

pws

Re: ZSH Shell support - Bug with a special character

[Frank Terbeck]

Peter Stephenson wrote:
> Tobias <tobias.basteiro@openenglish.com> wrote:
>> I'm just trying to run this script:
>>      git reset HEAD^
[...]
>>      zsh: no matches found: HEAD^
[...]
> If you don't need it, simply remove it from the start up file where it's
> turned on or add "unsetopt EXTENDED_GLOB" after whatever code is setting
> it.
>
> If you do need EXTENDED_GLOB for other purposes but don't need that
> particular syntax, and you have the latest version of zsh, you can turn
> off that pattern character,
>
> disable -p '^'

For completeness: Since ^ is just a globbing character with EXTENDED_GLOB,
like * or ? are with normal globbing, you can also just:

  % git reset 'HEAD^'

  or

  % git reset "HEAD^"

  or

  % git reset HEAD\^

But since the Tobias thought the behaviour was a bug, he' probably okay
with Peter's `disable' advice.


Regards, Frank

Re: ZSH Shell support - Bug with a special character

[Mikael Magnusson]

On 28 February 2014 20:54, Frank Terbeck <ft@bewatermyfriend.org> wrote:
> Peter Stephenson wrote:
>> Tobias <tobias.basteiro@openenglish.com> wrote:
>>> I'm just trying to run this script:
>>>      git reset HEAD^
> [...]
>>>      zsh: no matches found: HEAD^
> [...]
>> If you don't need it, simply remove it from the start up file where it's
>> turned on or add "unsetopt EXTENDED_GLOB" after whatever code is setting
>> it.
>>
>> If you do need EXTENDED_GLOB for other purposes but don't need that
>> particular syntax, and you have the latest version of zsh, you can turn
>> off that pattern character,
>>
>> disable -p '^'
>
> For completeness: Since ^ is just a globbing character with EXTENDED_GLOB,
> like * or ? are with normal globbing, you can also just:
>
>   % git reset 'HEAD^'
>
>   or
>
>   % git reset "HEAD^"
>
>   or
>
>   % git reset HEAD\^
>
> But since the Tobias thought the behaviour was a bug, he' probably okay
> with Peter's `disable' advice.

You can also just do
% git reset HEAD~
which has the advantage of not being shifted on american keyboards,
and doesn't require escaping in zsh. (As a side note, you can also do
git symbolic-ref h HEAD and then you can say git reset h~ (yes, I'm
very lazy)).

-- 
Mikael Magnusson

Re: ZSH Shell support - Bug with a special character

[Aaron Schrab]

>> Peter Stephenson wrote:
>>> If you don't need it, simply remove it from the start up file where 
>>> it's turned on or add "unsetopt EXTENDED_GLOB" after whatever code 
>>> is setting it.

One could also do `setopt NULL_GLOB`.  Which would get behaviour closer 
to the default from bash when a glob pattern doesn't match anything.  
Although that can lead to getting accustomed to not quoting things that 
should be which could come back to bite you later.

At 22:18 +0100 28 Feb 2014, Mikael Magnusson <mikachu@gmail.com> wrote:
>You can also just do
>% git reset HEAD~
>which has the advantage of not being shifted on american keyboards,
>and doesn't require escaping in zsh.

The ~ character requires shift on every American keyboard that I've ever 
used, and I'm an American.

While this is a suitable alternative when used by itself, and I use it 
myself for this very reason, it may be important to note that ~ and ^ 
are not equivalent if followed by a number.  A trailing number is valid 
after either one, but the meaning is very different.  And translating 
from ^ to ~ in that case is likely to produce a result, but not the 
intended result; translating the other way would be more likely to 
result in an error.

>(As a side note, you can also do
>git symbolic-ref h HEAD and then you can say git reset h~ (yes, I'm
>very lazy)).

Starting with git 1.8.5, `@` is a builtin alias for HEAD.