Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: bugs and features (was: Group, Summary buffers: End of line contain whitespaces)
Date: Fri, 29 Aug 2008 10:12:06 -0500	[thread overview]
Message-ID: <86zlmvkg8p.fsf_-_@lifelogs.com> (raw)
In-Reply-To: <87zlmwoyvs.fsf@marauder.physik.uni-ulm.de>

On Fri, 29 Aug 2008 13:15:51 +0200 Reiner Steib <reinersteib+gmane@imap.cc> wrote: 

RS> IMHO it's a minor cosmetic "problem".

RS> There are dozens of real bugs that are more important to fix: I have
RS> ~200 ticked articles in ding and more in gnus.gnus-bug and
RS> gmane.emacs.*.  Most of them are bug reports for Gnus.  I hoped to be
RS> able to at least forward them to the Emacs bug tracker.  AFAIK,
RS> there's not Emacs/Gnus function to do this conveniently yet [1].

I wish I could work on more issues: it's for lack of time and not for
lack of interest that I've been less productive.

Daiki Ueno's fix for IMAP also needs to be examined; that and Vitaly's
IMAP and backend patches are a pretty major undertaking.

I also need to write the gnus-registry documentation sometime this century.

RS> So, if you think is worth to care about this trailing whitespace in
RS> the Summary buffer, I won't object.  But I think there's much more
RS> useful and important work to do.

I agree.  But we had a patch, and it annoyed more than one person
apparently.

Ted




  reply	other threads:[~2008-08-29 15:12 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 ` Group, Summary buffers: End of line contain whitespaces 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           ` Ted Zlatanov [this message]
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
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=86zlmvkg8p.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).