Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ksinya@quartz.ocn.ne.jp
Subject: Gnus doesn't update nntp marks files when unplugged
Date: Tue, 31 Jan 2006 21:23:47 +0900	[thread overview]
Message-ID: <b4mzmlc7fho.fsf@jpl.org> (raw)

Hi,

Sin'ya Kanematsu reported that .marks files for nntp groups
aren't updated when Gnus is unplugged.  He usually do the
following:

1. Make sure Gnus is plugged (type `J j' if needed).
2. Type `g'.
3. Type `J s'.
4. Type `J j' to make Gnus be unplugged; type `s' to save.
5. Select a group of which the level is 1 using the `=' key. [*]
6. Read articles that have been downloaded; type `@' to instruct
   Gnus to download new articles. [**]
7. Exit the group.
8. Do 5,6,7 repeatedly.

[*] He has set `gnus-agent-handle-level' to 2, though he doesn't
 have group of which the level is 2.
[**] He has set it up not to download articles by default
 because of a lot of spam.

Although I'm not familiar with unplugged operations, I also
confirmed .marks files for nntp groups aren't updated when
Gnus is unplugged.  I did:

1. Make sure Gnus is plugged.
2. Type `J u' on a group in which there're unread articles.
3. Type `J j' to make Gnus be unplugged and read articles in the
 group in question.
4. Check whether the .marks file is updated.

Is there a thing that we need to do further?  Or is it simply a
bug?

Thanks in advance.



             reply	other threads:[~2006-01-31 12:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-31 12:23 Katsumi Yamaoka [this message]
2006-02-01  4:51 ` Katsumi Yamaoka
2006-02-01 12:46   ` Simon Josefsson
2006-02-02  9:33     ` Katsumi Yamaoka
2006-04-12 10:39       ` Lars Magne Ingebrigtsen
2006-04-18  8:50         ` Simon Josefsson
2006-04-18 16:27           ` 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=b4mzmlc7fho.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --cc=ksinya@quartz.ocn.ne.jp \
    /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).