[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Misbehaving gnus-gcc-mark-as-read while archiving to current group

From: Emanuel Berg
Subject: Re: Misbehaving gnus-gcc-mark-as-read while archiving to current group
Date: Wed, 06 Aug 2014 00:41:53 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)

Carlos Pita <> writes:

> ... But then there are a lot of quirks I'm not sure
> what to do about. Say I reply a message in "micro2"
> group. My reply is indeed archived to "micro2"...

I don't use exactly your setup - I have:

(setq gnus-gcc-mark-as-read t)
(setq gnus-message-archive-group '("nnml:mail.sent"))

> ... but in the summaries buffer:
> 1. At first the sent reply is not shown at all.

Did you enter the archive group from the group buffer
or did you just change buffer to the summary buffer
like between any other pair buffers? If you just
changed buffer to the summary, it'll be the same
summary as you left it.

> 2. If I press /N, then the reply is shown

Yes, that makes sense:
gnus-summary-insert-new-articles to refresh/update.

> but as unread.

What mark do they have? Mine has `O', which reads:

    Articles that were marked as read in previous
    sessions and are now "old" (`gnus-ancient-mark').

I.e., technically, they are "read".

> 3. If I press M-g, then the reply is shown read.

Yes, M-g is gnus-summary-rescan-group which ends with
gnus-summary-select-article if you check out the code.
So, M-g doesn't change the mark of the post per se - it
shows the posts, so the mark gets changed along the way.

> Is this a bug? In any case, it seems a very
> misleading behavior to me.

I don't think it is a bug, it is rather Gnus can be all
over the place sometimes. What happens at place A
doesn't show at place B because B is just a buffer
showing stuff and less no one tells it it should
refresh it doesn't. I myself haven't found a good way
to consistently have everything in synch - do tell, if
anyone knows. Everything that changes the state should
trigger the refresh of all Gnus buffers, I think.

I have lots of glue to achieve an imperfect
implementation of that idea, e.g., when you exit from a
summary buffer, whatever you did there should be
visible in the Group buffer - this wouldn't do with
hooks so I wrote:

(defun gnus-summary-exit-and-update-group ()
  (gnus-summary-save-newsrc t) ; FORCE
  (gnus-group-refresh) )

where the last line does that for my configuration (it
is not a standard Gnus function).

But even that isn't good as the ultimate would be
"global Gnus" + newsrc file consistency immediately on
the change of mark for a single post. That I'd like -
underground experts united

reply via email to

[Prev in Thread] Current Thread [Next in Thread]