From: Eli Zaretskii <eliz@gnu.org>
To: Werner LEMBERG <wl@gnu.org>
Cc: ofv@wanadoo.es, emacs-devel@gnu.org
Subject: Re: `bzr viz' slooow
Date: Wed, 27 Jan 2010 07:05:48 -0500 [thread overview]
Message-ID: <E1Na6ea-0002LN-29@fencepost.gnu.org> (raw)
In-Reply-To: <20100127.125133.183018597.wl@gnu.org> (message from Werner LEMBERG on Wed, 27 Jan 2010 12:51:33 +0100 (CET))
> Date: Wed, 27 Jan 2010 12:51:33 +0100 (CET)
> From: Werner LEMBERG <wl@gnu.org>
> Cc: emacs-devel@gnu.org
>
>
> > I'll try qlog.
>
> Well, it is indeed much faster in displaying the log tree. However,
> it has different weaknesses: Clicking on a commit from a branch (I
> mean the pink stuff like rev. 99322.1.8, however it is named) to see
> the diff, I have to wait almost 30 seconds until it gets displayed.
> Additionally, there doesn't seem to be a possibility to configure the
> behaviour of the `diff' window (for example, I would like to always
> start it in unidiff mode).
Maybe Someone(TM) should simply add a version DAG display to Emacs's
VC. (Maybe it even already exists, I don't know.) Don't we have
enough infrastructure in tree-widget to make that possible? Nothing
will ever be as customizable as Emacs.
next prev parent reply other threads:[~2010-01-27 12:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 17:05 `bzr viz' slooow Werner LEMBERG
2010-01-26 17:48 ` Eli Zaretskii
2010-01-26 22:07 ` Werner LEMBERG
2010-01-27 4:11 ` Eli Zaretskii
2010-01-27 6:14 ` Werner LEMBERG
2010-01-27 11:29 ` Eli Zaretskii
2010-01-27 12:01 ` Werner LEMBERG
2010-01-27 13:03 ` Eli Zaretskii
2010-01-26 18:37 ` Óscar Fuentes
2010-01-26 22:16 ` Werner LEMBERG
2010-01-26 23:13 ` Óscar Fuentes
2010-01-27 6:15 ` Werner LEMBERG
2010-01-26 22:59 ` Dan Nicolaescu
2010-01-27 5:22 ` Ken Hori
2010-01-27 6:02 ` Werner LEMBERG
2010-01-27 11:10 ` Óscar Fuentes
2010-01-27 11:30 ` Werner LEMBERG
2010-01-27 11:51 ` Werner LEMBERG
2010-01-27 12:05 ` Eli Zaretskii [this message]
2010-01-27 12:27 ` Óscar Fuentes
2010-01-27 13:02 ` Eli Zaretskii
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=E1Na6ea-0002LN-29@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=ofv@wanadoo.es \
--cc=wl@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.