From: Jonas Fonseca <fonseca@diku.dk>
To: Pascal Obry <pascal@obry.net>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] tig-0.11
Date: Sun, 4 May 2008 21:02:04 +0200 [thread overview]
Message-ID: <20080504190204.GA25329@diku.dk> (raw)
In-Reply-To: <481CD4E9.3080709@obry.net>
Hello Pascal,
Pascal Obry <pascal@obry.net> wrote Sat, May 03, 2008:
> 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.
Great that you noticed.
About your suggestion, Jeff suggested something similar for the blame
view when jumping to parents ealier in this thread. I will put in the
TODO list an entry about adding a general mechanism for saving and
restoring states across reloads and refreshes. The status and tree
views already have something like this and the stage and blame view are
good candidates as well. When the main view will support refreshing
there will be one more potential user.
--
Jonas Fonseca
prev parent reply other threads:[~2008-05-05 13:44 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
2008-05-04 19:02 ` Jonas Fonseca [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=20080504190204.GA25329@diku.dk \
--to=fonseca@diku.dk \
--cc=git@vger.kernel.org \
--cc=pascal@obry.net \
/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).