From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: When did backend marks become mandatory?
Date: Wed, 01 Sep 2010 18:05:29 +0200 [thread overview]
Message-ID: <m3d3sxqwja.fsf@quimbies.gnus.org> (raw)
I get the following error now and then:
Error reading nntp marks file /home/larsi/News/marks/news.eternal-september.org/comp/emacs/ ((error IO error reading /home/larsi/News/marks/news.eternal-september.org/comp/emacs/: Is a directory)). Continuing will use marks from .newsrc.eld. Continue? (y or n)
I haven't requested backend marks, and I don't want them. And I can't
find any way to disable them. Would anybody mind very much if I
introduce a `gnus-user-marks' variable and default it to nil? That'd
probably speed up normal Gnus usage greatly.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next reply other threads:[~2010-09-01 16:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 16:05 Lars Magne Ingebrigtsen [this message]
2010-09-01 16:21 ` Teemu Likonen
2010-09-01 20:20 ` 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=m3d3sxqwja.fsf@quimbies.gnus.org \
--to=larsi@gnus.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).