[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Referring to revisions in the git future.
From: |
Eli Zaretskii |
Subject: |
Re: Referring to revisions in the git future. |
Date: |
Sat, 01 Nov 2014 12:13:35 +0200 |
> Date: Sat, 1 Nov 2014 09:46:04 +0000
> From: Alan Mackenzie <address@hidden>
> Cc: "Stephen J. Turnbull" <address@hidden>, address@hidden
>
> On Sat, Nov 01, 2014 at 08:49:34AM +0100, David Kastrup wrote:
> > It's not like anybody's going to want to type off "abbreviations" by
> > hand anyway: too error-prone.
>
> I'm going to want to do this, that's why I started this thread. Using a
> computer to kill and yank such a number is going to be such a downer. Do
> you also kill and yank a variable name each time you need to type it in,
> or do you just type it?
I suggest "M-/" instead, I'm using that with bzr revno's as well.
It's way better than copy/paste, and usually is right on target after
you type the first 2 characters. Sometimes I need to type M-/ twice.
- Re: Referring to revisions in the git future., Tassilo Horn, 2014/11/01
- Re: Referring to revisions in the git future., David Kastrup, 2014/11/01
- Re: Referring to revisions in the git future., Alan Mackenzie, 2014/11/01
- Re: Referring to revisions in the git future., David Kastrup, 2014/11/01
- Re: Referring to revisions in the git future., Alan Mackenzie, 2014/11/01
- Re: Referring to revisions in the git future, Ivan Shmakov, 2014/11/01
- Re: Referring to revisions in the git future, Alan Mackenzie, 2014/11/01
- Re: Referring to revisions in the git future, Stephen J. Turnbull, 2014/11/01