[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Referring to revisions in the git future.
From: |
Alan Mackenzie |
Subject: |
Re: Referring to revisions in the git future. |
Date: |
Sat, 1 Nov 2014 13:21:50 +0000 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
Hello, Eli.
On Sat, Nov 01, 2014 at 03:06:40PM +0200, Eli Zaretskii wrote:
> > Date: Sat, 1 Nov 2014 11:33:38 +0000
> > From: Alan Mackenzie <address@hidden>
> > Cc: address@hidden, address@hidden, address@hidden
> > > 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.
> > Thanks, I didn't know about M-/.
> Really? So do you always type the names of your variable in their
> entirety? M-/ is a great savior of keystrokes for that.
Yes, and yes. I'm a reasonably fast typist, so it doesn't bother me
most of the time. But I will try M-/.
--
Alan Mackenzie (Nuremberg, Germany).
- 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
- Re: Referring to revisions in the git future., David Kastrup, 2014/11/01