Gnus development mailing list
 help / color / mirror / Atom feed
From: Karl Kleinpaste <karl@charcoal.com>
Subject: nnml as primary select method /vs/ gnus-inews-mark-gcc-as-read
Date: Thu, 02 Aug 2001 11:42:31 -0400	[thread overview]
Message-ID: <vxkelqulb88.fsf@cinnamon.vanillaknot.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1322 bytes --]

I changed my environment so that nnml is my primary select method.
This has made a bad interaction between gnus-message-archive-group and
gnus-inews-mark-as-read.

My gnus-message-archive-group consists of (MATCH . GROUP) pairs.  The
interpretation of the GROUP in the absence of a method prefix assumes
that nnarchive will be used, but I want to Gcc right into my nnml
groups, which don't normally have a prefix because they're primary
method groups.  Nonetheless, I can put an "nnml:" prefix on them
anyway, so the storing of articles works as I intended.

However, because of the slight difference in the perception of the
method (implicit method normally, with an exceptional case to avoid
nnarchive interpretation in g-m-a-g), the call to
gnus-group-mark-article-read fails to achieve the marking-as-read
result desired.

I would like to make the following small change in order to get around
this problem, but I'm not sure it won't break something else in the
(probably much more typical) case where the mail backend used for Gcc
is a secondary method.  What's needed is to ensure that, ultimately,
the group is referred to in its most "natural" way, which is to say,
with the implicit method of primary groups.

Could this be reviewed and applied if it's safe?  If it's not safe, is
there an alternative solution?


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Gcc mark-as-read fix --]
[-- Type: text/x-patch, Size: 433 bytes --]

--- gnus-msg.el.~1~	Thu Jul 26 01:05:45 2001
+++ gnus-msg.el	Thu Aug  2 11:21:27 2001
@@ -1243,7 +1243,7 @@
 			      group (gnus-status-message method))
 		(sit-for 2))
 	      (when (and group-art gnus-inews-mark-gcc-as-read)
-		(gnus-group-mark-article-read group (cdr group-art)))
+		(gnus-group-mark-article-read (car group-art) (cdr group-art)))
 	      (kill-buffer (current-buffer)))))))))
 
 (defun gnus-inews-insert-gcc ()

             reply	other threads:[~2001-08-02 15:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-02 15:42 Karl Kleinpaste [this message]
2001-08-02 20:49 ` Kai Großjohann
2001-08-02 21:11   ` Karl Kleinpaste
2001-08-02 21:54     ` Kai Großjohann
2001-08-17 10:29       ` Lars Magne Ingebrigtsen
2001-08-17 11:36         ` Kai Großjohann
2001-08-17 12:05           ` Lars Magne Ingebrigtsen
2001-08-17 13:34         ` Nevin Kapur
2001-08-17 13:57           ` Lars Magne Ingebrigtsen
2001-08-17 16:26             ` Doc strings for virtual server params (was Re: nnml as ...) Nevin Kapur
2001-08-17 16:33               ` 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=vxkelqulb88.fsf@cinnamon.vanillaknot.com \
    --to=karl@charcoal.com \
    /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).