From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: elp-wrapper sneaking into .newsrc.eld
Date: Mon, 06 Dec 2010 22:01:10 +0100 [thread overview]
Message-ID: <87y682wr8p.fsf@dod.no> (raw)
In-Reply-To: <m3ipz710zd.fsf@quimbies.gnus.org>
>>>>> Lars Magne Ingebrigtsen <larsi@gnus.org>:
> If you have a hierarchy of data, it's as easy to mess up the hierarchy
> as to mess up a file, really. Unless you know what you're doing.
Yes. But it is easier to navigate to the relevant part in a smaller
file, and easier to do the right thing. And, as I said, it will only
break one group, and not all of them.
But anyway, the most important thing is to separate the tick marks from
this stuff:
>> - I would like to have my manually edited stuff (group parameters, and
>> servers, and perhaps other stuff) out of .newsrc.eld and into a file,
>> or set of files, that can be version controlled and shared together
>> with the rest of the configuration files in my home directory
> Yes, that would be nice, but I don't really see that as essential. I
> mean, no other mail reader separates out per-group conf stuff like that.
Actually, the manually edited stuff could all still continue to exist in
a single file. It isn't a huge amount of stuff compared to the tick
marks, so it could be nicely formatted and more human readable (and
version control system friendly).
next prev parent reply other threads:[~2010-12-06 21:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-05 21:44 Dan Christensen
2010-12-05 21:52 ` Lars Magne Ingebrigtsen
2010-12-05 22:00 ` Dan Christensen
2010-12-05 22:38 ` Lars Magne Ingebrigtsen
2010-12-05 23:28 ` Dan Christensen
2010-12-06 8:31 ` Steinar Bang
2010-12-06 9:33 ` Vegard Vesterheim
2010-12-06 13:29 ` Lars Magne Ingebrigtsen
2010-12-06 20:56 ` Steinar Bang
2010-12-15 16:34 ` Ted Zlatanov
2010-12-15 19:41 ` Steinar Bang
2010-12-15 20:59 ` Ted Zlatanov
2010-12-06 13:31 ` Lars Magne Ingebrigtsen
2010-12-06 21:01 ` Steinar Bang [this message]
2010-12-15 16:36 ` Ted Zlatanov
2010-12-15 19:11 ` Lars Magne Ingebrigtsen
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=87y682wr8p.fsf@dod.no \
--to=sb@dod.no \
--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).