From: Kevin Ryde <user42@zip•com.au>
To: "David Kågedal" <davidk@lysator•liu.se>
Cc: Jakub Narebski <jnareb@gmail•com>, Sergei Organov <osv@javad•com>,
Andreas Schwab <schwab@linux-m68k•org>,
git@vger•kernel.org, 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: Sat, 05 Feb 2011 08:49:26 +1100 [thread overview]
Message-ID: <87pqr7a2s9.fsf@blah.blah> (raw)
In-Reply-To: <87r5bom7g3.fsf@krank.kagedal.org> ("David Kågedal"'s message of "Fri, 04 Feb 2011 11:15:40 +0100")
David Kågedal <davidk@lysator•liu.se> writes:
>
> But we can
> of course let the echo area grow to two lines, or even three.
Though xemacs 21 can't grow it, and emacs doesn't if you turn off
message-truncate-lines.
If message-truncate-lines is nil or unbound you might collapse out
newlines or perhaps ellipsize or something.
next prev parent reply other threads:[~2011-02-04 22:21 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
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 ` Kevin Ryde [this message]
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=87pqr7a2s9.fsf@blah.blah \
--to=user42@zip$(echo .)com.au \
--cc=davidk@lysator$(echo .)liu.se \
--cc=enselic@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=jnareb@gmail$(echo .)com \
--cc=jrnieder@gmail$(echo .)com \
--cc=julliard@winehq$(echo .)org \
--cc=osv@javad$(echo .)com \
--cc=schwab@linux-m68k$(echo .)org \
--cc=zedek@gnu$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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