From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: gnus-sync: `gnus-newsrc-alist' modifications don't survive `M-g'
Date: Fri, 06 Jan 2012 21:36:09 -0500 [thread overview]
Message-ID: <87mxa0s0h2.fsf@lifelogs.com> (raw)
In-Reply-To: <m3d3awdz2q.fsf@stories.gnus.org>
On Sat, 07 Jan 2012 03:30:05 +0100 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
LMI> Ted Zlatanov <tzz@lifelogs.com> writes:
>> Hmm, no. After removing the .marks and then `s'aving the newsrc.eld:
>>
>> % find ~/News -name .marks
>>
>> /home/tzz/News/marks/news.gmane.org/gmane.emacs.devel/.marks
>> /home/tzz/News/marks/news.gmane.org/gmane.emacs.gnus.general/.marks
>> /home/tzz/News/marks/news.gmane.org/gmane.emacs.tramp/.marks
>>
>> I'm using a Gnus Git checkout from 5 days ago. I don't think I've
>> requested these marks files in my settings.
LMI> The variable that controls this is... er... `gnus-propagate-marks'?
Sorry, it's nil for me.
*Messages* says:
Exiting summary buffer and applying spam rules
Bootstrapping marks for gmane.emacs.gnus.general...done
Bootstrapping marks for gmane.emacs.devel...done
Bootstrapping marks for gmane.emacs.tramp...done
gnus-sync-newsrc-loader-builder: add nntp+news.gmane.org:gmane.emacs.gnus.general, it's modified
Could gnus-sync.el be doing something? I would think not.
Ted
next prev parent reply other threads:[~2012-01-07 2:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 12:42 Ted Zlatanov
2011-11-03 22:36 ` Lars Magne Ingebrigtsen
2011-11-04 12:21 ` Ted Zlatanov
2012-01-03 23:08 ` Lars Magne Ingebrigtsen
2012-01-07 1:36 ` Ted Zlatanov
2012-01-07 1:40 ` Lars Magne Ingebrigtsen
2012-01-07 2:18 ` Ted Zlatanov
2012-01-07 2:23 ` Ted Zlatanov
2012-01-07 2:30 ` Lars Magne Ingebrigtsen
2012-01-07 2:36 ` Ted Zlatanov [this message]
2012-01-07 6:25 ` Lars Magne Ingebrigtsen
2012-01-08 10:47 ` Steinar Bang
2012-01-16 18:46 ` Steinar Bang
2012-01-26 18:56 ` Lars Ingebrigtsen
2012-01-26 21:20 ` Steinar Bang
2012-01-26 22:08 ` Lars 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=87mxa0s0h2.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).