unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: 10238@debbugs.gnu.org, Andreas Schwab <schwab@linux-m68k.org>,
	ding@gnus.org
Subject: bug#10238: R in gnus-summary does not pop a frame like F does
Date: Wed, 25 Jan 2012 23:56:49 +0100	[thread overview]
Message-ID: <878vkvgzm6.fsf@gnus.org> (raw)
In-Reply-To: <87wr8fhloi.fsf@lifelogs.com> (Ted Zlatanov's message of "Wed, 25 Jan 2012 09:00:13 -0600")

Ted Zlatanov <tzz@lifelogs.com> writes:

> But forcing the Gnus developers to use 80 chars in their own work
> seems too harsh.

I don't mind the 80-character limit.  But it can be kinda repetitive if
the 80-character summary just repeats a shortened version of the long
explanation underneath.

-- 
(domestic pets only, the antidote for overdose, milk.)
  http://lars.ingebrigtsen.no  *  Sent from my Rome





  reply	other threads:[~2012-01-25 22:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-06 21:20 bug#10238: R in gnus-summary does not pop a frame like F does Stefan Monnier
2012-01-04 21:01 ` Lars Magne Ingebrigtsen
2012-01-05  1:26   ` Stefan Monnier
2012-01-05  5:01     ` Lars Magne Ingebrigtsen
2012-01-05 21:47       ` Stefan Monnier
2012-01-06  3:19         ` Lars Magne Ingebrigtsen
     [not found]     ` <87pqe8kbg1.fsf@lifelogs.com>
2012-01-24 21:25       ` Eli Zaretskii
     [not found]       ` <83pqe823oj.fsf@gnu.org>
2012-01-24 22:34         ` Ted Zlatanov
     [not found]         ` <87vco0ivb1.fsf@lifelogs.com>
2012-01-24 23:02           ` Andreas Schwab
2012-01-25  6:30             ` Eli Zaretskii
2012-01-25 15:00               ` Ted Zlatanov
2012-01-25 22:56                 ` Lars Ingebrigtsen [this message]
2012-01-26 15:34                   ` Ted Zlatanov
2012-01-30 22:45                 ` Lars Ingebrigtsen
2012-01-31  1:46                   ` Stefan Monnier
2012-01-24 22:00     ` Ted Zlatanov

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=878vkvgzm6.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=10238@debbugs.gnu.org \
    --cc=ding@gnus.org \
    --cc=schwab@linux-m68k.org \
    --cc=tzz@lifelogs.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.
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).