Gnus development mailing list
 help / color / mirror / Atom feed
From: Michael Olson <mwolson@member.fsf.org>
To: ding@gnus.org
Subject: Re: .newsrc.eld should have one newline per group
Date: Wed, 05 Dec 2007 00:26:54 -0500	[thread overview]
Message-ID: <87k5ntsodd.fsf@grepfind.mwolson.org> (raw)
In-Reply-To: <873auktzlo.fsf_-_@jidanni.org> (jidanni@jidanni.org's message of "Mon, 03 Dec 2007 08:02:11 +0800")

[-- Attachment #1: Type: text/plain, Size: 665 bytes --]

jidanni@jidanni.org writes:

> Gentlemen, I propose instead of a paltry 13 newlines,
> $ wc .newsrc.eld
>     13  44047 859072 .newsrc.eld
> we instead maintain .newsrc.eld with one newline per newsgroup, yes
> lisp indented, but minimally.

I fully agree.  I recently had to selectively restore items from a
backed-up .newsrc.eld file, and Emacs took a long time to move around in
that file.

-- 
       Michael Olson -- FSF Associate Member #652     |
 http://mwolson.org/ -- Jabber: mwolson_at_hcoop.net  |  /` |\ | | |
          Programmer -- Hobbies: Lisp, HCoop          | |_] | \| |_|
Projects: Emacs, Muse, ERC, EMMS, ErBot, DVC, Planner |

[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]

  parent reply	other threads:[~2007-12-05  5:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-30  0:58 how to delete groups despite backend jidanni
2007-11-30  1:22 ` Dave Goldberg
2007-11-30  1:32 ` Katsumi Yamaoka
2007-12-03  0:02   ` .newsrc.eld should have one newline per group jidanni
2007-12-03 23:55     ` jidanni
2007-12-04  1:27       ` jidanni
2007-12-05  5:26     ` Michael Olson [this message]
2007-12-05 23:18       ` James Cloos
2007-12-06  7:35         ` Reiner Steib
2007-12-07  1:00           ` reader
2007-12-06  8:35         ` Daniel Pittman
2007-12-06 12:43         ` jidanni
2007-12-03  0:11   ` how to delete groups despite backend jidanni

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=87k5ntsodd.fsf@grepfind.mwolson.org \
    --to=mwolson@member.fsf.org \
    --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).