Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Group, Summary buffers: End of line contain whitespaces
Date: Fri, 29 Aug 2008 10:55:56 -0500	[thread overview]
Message-ID: <864p53ke7n.fsf@lifelogs.com> (raw)
In-Reply-To: <874p53kfcj.fsf@broken.deisui.org>

On Sat, 30 Aug 2008 00:31:24 +0900 Daiki Ueno <ueno@unixuser.org> wrote: 

DU> Ted Zlatanov <tzz@lifelogs.com> writes:
>> On Thu, 28 Aug 2008 08:01:56 +0900 Miles Bader <miles@gnu.org> wrote: 
>> 
MB> Ted Zlatanov <tzz@lifelogs.com> writes:
>>>> I think this is the right solution.  No one has explained why we need
>>>> the trailing spaces AFAIK.
>> 
MB> I don't think anyone has claimed they're _needed_.  It's more than they
MB> aren't particularly harmful, and going to great lengths to avoid them is
MB> silly.
>> 
>> I don't think it's silly: we're producing unneeded data for no clear
>> purpose, and there's no harm in removing it.  If so, it should be
>> removed.  I can do it unless someone explains why I shouldn't.

DU> I also think that it's silly.  After the patch applied,

DU> (gnus-parse-format "%A" '((?A "ABCDE   " ?s)))
DU> => (concat "ABCDE   ")

DU> (gnus-parse-format "%A" '((?A "ABCDE   " ?s)) t)
DU> => "ABCDE"

DU> Future Gnus developers will be troubled with the difference of the
DU> results.  Also, this change makes gnus-parse-simple-format specific for
DU> rendering *Group* and *Summary* lines.  That's a layer breakage.

DU> I think Katsumi's first approach is even better.

Before I revert and apply the other patch, I'd like to hear what Katsumi
thinks.  I agree format and layer breakage is bad, and don't want to
break more inadvertently.

Thanks
Ted




  reply	other threads:[~2008-08-29 15:55 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87abfkmuko.fsf@jondo.cante.net>
2008-08-13  8:29 ` Katsumi Yamaoka
2008-08-13 18:56   ` Reiner Steib
2008-08-13 21:47     ` Jari Aalto
2008-08-15 16:31       ` jidanni
2008-08-19 11:48       ` Miles Bader
2008-08-22 15:52   ` Ted Zlatanov
2008-08-27 23:01     ` Miles Bader
2008-08-28 13:51       ` Ted Zlatanov
2008-08-29 11:15         ` Reiner Steib
2008-08-29 15:12           ` bugs and features (was: Group, Summary buffers: End of line contain whitespaces) Ted Zlatanov
2008-09-15 21:00             ` registry doc patch (was: bugs and features) Ted Zlatanov
2008-09-16  9:17               ` registry doc patch Rupert Swarbrick
2008-09-16 13:36                 ` Ted Zlatanov
2008-09-16 12:30               ` Magnus Henoch
2008-09-16 13:39                 ` Ted Zlatanov
2008-09-18 23:19                   ` Katsumi Yamaoka
2008-09-19 16:19                     ` Ted Zlatanov
2008-09-23 19:18                       ` Reiner Steib
2008-09-24  0:37                         ` Katsumi Yamaoka
2008-09-24  6:45                           ` Katsumi Yamaoka
2008-09-24 16:45                             ` Reiner Steib
2008-09-24 16:44                           ` informat.el: `Info-split' split size (was: registry doc patch) Reiner Steib
2008-09-24 23:58                             ` informat.el: `Info-split' split size Katsumi Yamaoka
2008-09-25  3:10                               ` Eli Zaretskii
2008-09-25  4:01                                 ` Katsumi Yamaoka
2008-09-25 23:10                               ` Katsumi Yamaoka
2008-08-29 13:51         ` Group, Summary buffers: End of line contain whitespaces Ted Zlatanov
2008-08-29 15:31         ` Daiki Ueno
2008-08-29 15:55           ` Ted Zlatanov [this message]
2008-08-30  5:07             ` Katsumi Yamaoka
2008-08-30  9:33               ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=864p53ke7n.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.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 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 NNTP newsgroup(s).