unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: pointless buttons at end of VC log buffers
Date: Tue, 16 Feb 2010 06:38:40 +0100	[thread overview]
Message-ID: <87pr45zqn3.fsf@telefonica.net> (raw)
In-Reply-To: buomxz93i6p.fsf@dhlpc061.dev.necel.com

Miles Bader <miles.bader@necel.com> writes:

> If I do a vc log command (e.g., "C-x v L"), i get the log in a
> "*vc-change-log*" buffer, and at the veryyy end of the buffer, I see:
>
>    [Show 2X entries]    [Show unlimited entries]
>
> However these buttons seem useless, as the buffer already contains all
> log entries (about 1200)!
>
> * It seems like it should only show these buttons if the log listing
> gets interrupted for some reason.

For this, VC-log needs to count how many revisions it is showing and
compare with the number of revisions on the branch. Looks like too much
work. OTOH, on some backends (i.e. git) it is difficult to differentiate
the first (oldest) revision from any other on the log listing, as it
lacks revision numbers.

> Also, the formatting is a bit off, as the above buttons are not preceded
> by a newline... they're glommed onto end of the last line of the log
> listing.
>
> * So, some code should make sure there's a newline before the buttons --
>  indeed, it should probably add an entire blank line between the last
>  log line and the buttons so they stand out more (I didn't even notice
>  them for a while...).

It seems that git does not append a newline to the last revision. The
buttons look fine for Subversion and Bazaar, although a blank line
before them would be aesthetically pleasant.





  reply	other threads:[~2010-02-16  5:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-16  4:42 pointless buttons at end of VC log buffers Miles Bader
2010-02-16  5:38 ` Óscar Fuentes [this message]
2010-02-16  8:43   ` Miles Bader
2010-02-16 13:15     ` Óscar Fuentes
2010-02-16 13:54       ` Miles Bader
2010-02-16 16:49         ` Stefan Monnier
2010-02-17 22:36           ` Miles Bader

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pr45zqn3.fsf@telefonica.net \
    --to=ofv@wanadoo.es \
    --cc=emacs-devel@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).