From: Jonas Fonseca <jonas.fonseca@gmail.com>
To: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [tig PATCH v2 0/2] popup menu
Date: Wed, 25 Feb 2009 23:32:11 +0100 [thread overview]
Message-ID: <2c6b72b30902251432p18f7cb48sb5565cc200d5e3b9@mail.gmail.com> (raw)
In-Reply-To: <1235311778-11112-1-git-send-email-giuseppe.bilotta@gmail.com>
On Sun, Feb 22, 2009 at 15:09, Giuseppe Bilotta
<giuseppe.bilotta@gmail.com> wrote:
> Second version, in two patches. The first one is just the same as
> previous one, minus a couple of leftovers.
>
> The second one reimplements the menu drawing routine so that it can be
> called when necessary to redraw the menu entirely, e.g. after a resize
> or when background loading finishes.
I didn't read them through very carefully yet, so will "queue" them
for now until I get fully back to tig. There are still some quirks
that might needs to be addressed related with resizing, but this could
also be fixed later. Anyway, I would like to think a bit more whether
or not I like the cute menus, and also whether options might be served
better by introducing an option view.
Regarding the "tig branch", would you mind if I postpone applying it
until the branch view develops into something that is actually usable?
--
Jonas Fonseca
next prev parent reply other threads:[~2009-02-25 22:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-22 14:09 [tig PATCH v2 0/2] popup menu Giuseppe Bilotta
2009-02-22 14:09 ` [tig PATCH v2 1/2] Popup menu Giuseppe Bilotta
2009-02-22 14:09 ` [tig PATCH v2 2/2] Popup menu: redraw as needed Giuseppe Bilotta
2009-02-22 18:36 ` [tig PATCH v2bis " Giuseppe Bilotta
2009-02-25 22:32 ` Jonas Fonseca [this message]
2009-02-25 22:56 ` [tig PATCH v2 0/2] popup menu Giuseppe Bilotta
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=2c6b72b30902251432p18f7cb48sb5565cc200d5e3b9@mail.gmail.com \
--to=jonas.fonseca@gmail.com \
--cc=git@vger.kernel.org \
--cc=giuseppe.bilotta@gmail.com \
/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).