Confused about crosspost marking behavior.

[Rob Browning <rlb@cs.utexas.edu>]

I recently changed my setup to split some incoming messages to
multiple groups (more on that in my second question), and, as
expected, I had a message that was posted both to my inbox and another
group.  When I read that message in my inbox, I went ahead and marked
it as expirable.  When I went to the other group to check on it, it
wasn't there, so I figured it had also been marked as expirable.  When
I checked by re-entering the group with "C-u Enter", I found that it
had actually been marked as read.  Now I wouldn't have been surprised
if it had either been marked the same as I marked it in the other
group, or if it had not been marked at all, but to be marked
differently both places was unexpected.  (Also, it might be nice to be
able to choose whether or not a given command affects just the current
article, or all instances of it...)

As additional information, I use Kai's general approach (I think) to
handling my mail groups.  All my groups are auto-expire, and I have it
set up so that the normal movement commands default to marking
articles expirable, not "read".

  ;; Make sure all groups are auto-expire.
  (setq gnus-auto-expirable-newsgroups "^nnml")

  ;; Use this for auto-expire only.
  (remove-hook 'gnus-mark-article-hook
               'gnus-summary-mark-read-and-unread-as-read)
  (add-hook 'gnus-mark-article-hook 'gnus-summary-mark-unread-as-read)

-- 
Rob Browning <rlb@cs.utexas.edu> PGP=E80E0D04F521A094 532B97F5D64E3930