From: Pascal Obry <pascal@obry.net>
To: Jonas Fonseca <fonseca@diku.dk>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] tig-0.11
Date: Sat, 03 May 2008 23:11:05 +0200 [thread overview]
Message-ID: <481CD4E9.3080709@obry.net> (raw)
In-Reply-To: <20080406200533.GA20537@diku.dk>
Jonas,
I see that the '@' key can now move from chunk to chunk. This is nice
but it would be more user friendly if after staging a hunk the cursor
was not moved to the first line! I think it would be better to have the
cursor on top of the next hunk.
Pascal.
--
--|------------------------------------------------------
--| Pascal Obry Team-Ada Member
--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE
--|------------------------------------------------------
--| http://www.obry.net
--| "The best way to travel is by means of imagination"
--|
--| gpg --keyserver wwwkeys.pgp.net --recv-key C1082595
next prev parent reply other threads:[~2008-05-03 21:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-06 20:05 [ANNOUNCE] tig-0.11 Jonas Fonseca
2008-04-10 4:02 ` Jeff King
2008-04-10 8:56 ` Jonas Fonseca
2008-05-03 21:11 ` Pascal Obry [this message]
2008-05-04 19:02 ` Jonas Fonseca
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=481CD4E9.3080709@obry.net \
--to=pascal@obry.net \
--cc=fonseca@diku.dk \
--cc=git@vger.kernel.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.
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).