zsh-workers
 help / color / mirror / code / Atom feed
From: Aaron Schrab <aaron@schrab.com>
To: zsh-workers@zsh.org
Subject: Re: ZSH Shell support - Bug with a special character
Date: Fri, 28 Feb 2014 19:06:41 -0500	[thread overview]
Message-ID: <20140301000641.GF10369@pug.qqx.org> (raw)
In-Reply-To: <CAHYJk3TmmpEkhR9gtprrnNoV1t9uTiNp9Jx=vBkzCg6cxwTryw@mail.gmail.com>

>> 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.


      reply	other threads:[~2014-03-01  0:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-28 17:00 Tobias
2014-02-28 18:37 ` Peter Stephenson
2014-02-28 19:54   ` Frank Terbeck
2014-02-28 21:18     ` Mikael Magnusson
2014-03-01  0:06       ` Aaron Schrab [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=20140301000641.GF10369@pug.qqx.org \
    --to=aaron@schrab.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).