[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#10238: R in gnus-summary does not pop a frame like F does

From: Ted Zlatanov
Subject: bug#10238: R in gnus-summary does not pop a frame like F does
Date: Wed, 25 Jan 2012 09:00:13 -0600
User-agent: Gnus/5.110018 (No Gnus v0.18) Emacs/24.0.92 (gnu/linux)

On Wed, 25 Jan 2012 01:30:49 -0500 Eli Zaretskii <address@hidden> wrote: 

>> From: Andreas Schwab <address@hidden>
>> Cc: Eli Zaretskii <address@hidden>,  address@hidden,  address@hidden,  
>> address@hidden
>> Date: Wed, 25 Jan 2012 00:02:06 +0100
>> Ted Zlatanov <address@hidden> writes:
>> > We're talking about VCS commit messages, not docstrings.  It's a
>> > different context, and for VCS commits often there is information that
>> > needs to be distilled into that first line and 80 chars are not enough.
>> The summary line doesn't need to be precise.  It should just give an
>> informal overview of the change.

EZ> 100% agreement.

OK, but we're not talking about the destiny of the summary line in a VCS
commit, but rather whether it should be limited to 80 chars.

I think we should try to keep it under 80, and if it has to go over, the
essential information should be before the 80th char.  But forcing it to
80 will force us to write convoluted summaries that misrepresent the
commit for the sake of saving a few characters.

Please note we're talking about Gnus here, not Emacs.  We could ask
Yamaoka-san, who synchronizes Gnus into Emacs, to cut or rewrite long
commit summary lines so they don't bother Emacs developers.  But forcing
the Gnus developers to use 80 chars in their own work seems too harsh.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]