Gnus development mailing list
 help / color / mirror / Atom feed
From: Philipp Haselwarter <philipp.haselwarter@gmx.de>
To: ding@gnus.org
Subject: Re: Separating marks from other group configuration
Date: Tue, 14 Dec 2010 15:45:42 +0100	[thread overview]
Message-ID: <87wrnc2z1l.fsf@netarch.haselwarter.org> (raw)
In-Reply-To: <sa3r5dkaczb.fsf@cigue.easter-eggs.fr>

Julien Danjou <julien@danjou.info> writes:

> On Mon, Dec 13 2010, Lars Magne Ingebrigtsen wrote:
>
>> While making dinner here I was thinking about what Steinar said about
>> separating out the non-marks stuff (group parameters and...  stuff?)
>> from .newsrc.eld.  Which led me to thinking about where to store it.
>> Which led me to thinking about IMAP.
>
> As an IMAP-only user, I just want to say that the .newsrc.eld is a PITA
> to me.

+1
If at least it weren't that messy. But especially once gnus gets
confused with the number of mails in a group, things can get quite
obscure. Like, when I want to browse my inbox, which gnus claims to
contain about 3 times the messages it actually does, "/ o 100" often just
displays the last 15 messages.
Also, I have to subscribe to new groups on every site I use gnus, making
the whole configuration rather unportable.
Maybe it'd already help to refactor the .newsrc.eld? (I know you're not
supposed to edit that manually, but sometimes it just feels like you
need to get some control over things..)

In general, adding/editing groups in gnus instead of .gnus.el does
make it quite difficult to figure out what sate your config really is
in:
For example, on my notebook I added an rss feed in the group buffer, G m
and adding all the information. Now if I want the same feed elsewhere I
have to go through all that again. I'd really love to just get some
lisp snippets that I could directly dump into my .gnus.el.


-- 
Philipp Haselwarter




  parent reply	other threads:[~2010-12-14 14:45 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-13 17:57 Lars Magne Ingebrigtsen
2010-12-13 18:49 ` Steinar Bang
2010-12-13 19:14   ` Lars Magne Ingebrigtsen
2010-12-15 16:32   ` gnus-sync ideas (was: Separating marks from other group configuration) Ted Zlatanov
2010-12-15 19:18     ` gnus-sync ideas Lars Magne Ingebrigtsen
2010-12-15 21:26       ` Ted Zlatanov
2010-12-16 16:08         ` Lars Magne Ingebrigtsen
2010-12-16 17:19           ` Ted Zlatanov
2010-12-16 10:06     ` Julien Danjou
2010-12-16 16:33       ` Ted Zlatanov
2010-12-16 18:08         ` Steinar Bang
2010-12-17 15:55       ` Philipp Haselwarter
2010-12-17 16:12         ` Lars Magne Ingebrigtsen
2010-12-17 22:19           ` Steinar Bang
2010-12-18 13:45     ` Ted Zlatanov
2010-12-19 20:08     ` Steinar Bang
2010-12-27 15:22       ` Ted Zlatanov
2010-12-29 22:07         ` Steinar Bang
2010-12-14 10:02 ` Separating marks from other group configuration Julien Danjou
2010-12-14 12:04   ` Steinar Bang
2010-12-14 14:45   ` Philipp Haselwarter [this message]
2010-12-15 19:47     ` Lars Magne Ingebrigtsen
2010-12-15 20:29       ` Philipp Haselwarter
2010-12-15 20:32         ` Lars Magne Ingebrigtsen
2010-12-15 19:45   ` Lars Magne Ingebrigtsen
2010-12-15 20:38     ` Steinar Bang
2010-12-15 20:42       ` Lars Magne Ingebrigtsen
2010-12-16 10:12         ` Julien Danjou
2010-12-16 15:50           ` Lars Magne Ingebrigtsen
2010-12-16 16:17             ` Julien Danjou
2010-12-16 16:20               ` Lars Magne Ingebrigtsen
2010-12-16 16:27                 ` Julien Danjou
2010-12-16 16:33                   ` Lars Magne Ingebrigtsen
2010-12-16 16:49                     ` Julien Danjou
2010-12-16 16:18             ` 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=87wrnc2z1l.fsf@netarch.haselwarter.org \
    --to=philipp.haselwarter@gmx.de \
    --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).