unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>,
	Ding Mailing List <ding@gnus.org>
Cc: 10238@debbugs.gnu.org, Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: bug#10238: R in gnus-summary does not pop a frame like F does
Date: Tue, 24 Jan 2012 16:00:46 -0600	[thread overview]
Message-ID: <87pqe8kbg1.fsf__32243.0235137746$1327438923$gmane$org@lifelogs.com> (raw)
In-Reply-To: <jwvvcorymdh.fsf-monnier+INBOX@gnu.org> (Stefan Monnier's message of "Wed, 04 Jan 2012 20:26:38 -0500")

On Wed, 04 Jan 2012 20:26:38 -0500 Stefan Monnier <monnier@iro.umontreal.ca> wrote: 

>>> PS: BTW, please keep commit logs comments within the usual 80 (or even
>>> 72) columns!
>> I have previously been instructed to make the first line of a commit
>> message be a complete sentence.  Making it complete, less than 72
>> characters and meaningful is a challenge.

SM> The first line doesn't need to be complete, as far as I'm concerned.
SM> And I'm more worried about it staying within the 80 columns limit than
SM> about it being a complete sentence.
SM> IOW, just make sure that if you only read the first 80 chars of
SM> the first line, you get something meaningful that describes the bulk of
SM> the patch.

I'm OK with the above, as long as the Gnus developers are allowed to go
over 80 in the first line within reason.  So we'll keep the first line
short, but if it has to go a little over 80, we'll make sure the really
important stuff is at the very beginning.

Can we highlight past the 80th char in commit log buffers?  That would
be a nice passive indicator of a problem.

CC to ding for any stray comments.

Ted





      parent reply	other threads:[~2012-01-24 22:00 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
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 [this message]

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='87pqe8kbg1.fsf__32243.0235137746$1327438923$gmane$org@lifelogs.com' \
    --to=tzz@lifelogs.com \
    --cc=10238@debbugs.gnu.org \
    --cc=ding@gnus.org \
    --cc=larsi@gnus.org \
    --cc=monnier@iro.umontreal.ca \
    /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).