Re: Itches with the current rev spec
- From
Felipe Contreras <felipe.contreras@gmail.com>
- Date
- Apr 25, 2013, 08:48 UTC
- Message-ID
- <CAMP44s3P02yFoi64j5aROQm69O4NGzvzxONyEjkpvLzW-GTenA@mail.gmail.com>
- In-Reply-To
- <vpqehdzkoix.fsf@grenoble-inp.fr>
On Thu, Apr 25, 2013 at 3:22 AM, Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> wrote:
Show 31 quoted lines
> Ramkumar Ramachandra <artagnon@gmail.com> writes: > >> Hi, >> >> So, I have three serious itches that would be nice to address: >> >> 1. git reset --hard HEAD~1/ git show HEAD~1 is a very common idiom >> that's unnecessarily cumbersome to type out. We can make the <rev> >> part of <rev>~<n> optional without being ambiguous: you might argue >> that ~<n> normally refers to a /home/<n>, but who uses numbers in >> place of usernames? Even if they do, how can that path possibly be >> inside our repository? > > It's a bit more complex than that: the ~<username> is expanded by the > shell, before Git has any opportunity to guess anything. > > ~1 would be unusable for zsh users and tcsh users at least by default: > > zsh% echo ~1 > zsh: not enough directory stack entries. > > tcsh% echo ~1 > Unknown user: 1. > > (An obvious workaround is to shell-quote it, but as the goal is to have > something easy to type, \~1 or '~1' do not give so much benefit over > HEAD~1) > > That said, it seems to work fine for bash (even if the number is a PID, > it's not expanded), so it may be a good idea to add it as a shortcut, > with a warning in the doc about shell expansion.
Yeah, probably fine, but I would also like H~1.
-- Felipe Contreras