From: "David Kågedal" <davidk@lysator.liu.se>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Sergei Organov <osv@javad.com>,
Andreas Schwab <schwab@linux-m68k.org>,
git@vger.kernel.org, Kevin Ryde <user42@zip.com.au>,
Martin Nordholts <enselic@gmail.com>,
Alexandre Julliard <julliard@winehq.org>,
Xavier Maillard <zedek@gnu.org>,
Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: git-blame.el: does not show one-line summary in echo area
Date: Fri, 04 Feb 2011 11:15:40 +0100 [thread overview]
Message-ID: <87r5bom7g3.fsf@krank.kagedal.org> (raw)
In-Reply-To: <201102041103.10770.jnareb@gmail.com> (Jakub Narebski's message of "Fri, 4 Feb 2011 11:03:09 +0100")
Jakub Narebski <jnareb@gmail.com> writes:
> Dnia piątek 4. lutego 2011 10:53, David Kågedal napisał:
>
>> 3) Showing when you move to a different blame chunk, by showing a
>> one-line summary in the echo area.
>
> There is even some prior art for this to borrow from, namely cperl-mode
> shows information about syntax at given point in echo area (minibuffer
> area) after some delay. Just FYI.
Sure, there are a number of those (eldoc comes to mind). I think the
hardest part is figuring out what to show. A 40-charater hash is
probably not very useful. The problem is that the committer information,
date, and commit message first line takes up a lot of space. But we can
of course let the echo area grow to two lines, or even three.
I don't think I'll have time to cook something up right now, though.
--
David Kågedal
next prev parent reply other threads:[~2011-02-04 10:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-04 16:21 git-blame.el: what is format-spec? Sergei Organov
2009-12-04 16:38 ` Andreas Schwab
2009-12-04 16:59 ` Sergei Organov
2009-12-04 17:36 ` David Kågedal
2009-12-04 20:54 ` Sergei Organov
2009-12-06 18:43 ` David Kågedal
2009-12-07 8:36 ` Sergei Organov
2009-12-07 9:05 ` David Kågedal
2010-05-14 13:13 ` Alex Unleashed
2010-05-25 13:44 ` [PATCH] git-blame.el: Add (require 'format-spec) David Kågedal
2010-10-29 3:38 ` [PATCH resend] " Jonathan Nieder
2011-02-04 1:43 ` git-blame.el: does not show one-line summary in echo area Jonathan Nieder
2011-02-04 9:53 ` David Kågedal
2011-02-04 10:03 ` Jakub Narebski
2011-02-04 10:15 ` David Kågedal [this message]
2011-02-04 12:26 ` David Kågedal
2011-02-11 2:29 ` Jonathan Nieder
2011-02-11 6:42 ` git-blame.el: format of date strings Jonathan Nieder
2011-02-11 7:56 ` Martin Nordholts
2012-06-10 8:24 ` [PATCH/RFC] git-blame.el: truncate author to avoid jagged left edge of code Jonathan Nieder
2013-01-29 20:17 ` David Kågedal
2011-02-04 21:49 ` git-blame.el: does not show one-line summary in echo area Kevin Ryde
2009-12-04 17:42 ` git-blame.el: what is format-spec? Andreas Schwab
2009-12-04 18:18 ` Matthieu Moy
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=87r5bom7g3.fsf@krank.kagedal.org \
--to=davidk@lysator.liu.se \
--cc=enselic@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=jrnieder@gmail.com \
--cc=julliard@winehq.org \
--cc=osv@javad.com \
--cc=schwab@linux-m68k.org \
--cc=user42@zip.com.au \
--cc=zedek@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.
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.