Marking replies that are gcc'd to the same group

Marking replies that are gcc'd to the same group

[Sacha Chua]

I use (setq gnus-gcc-mark-as-read t) and Oort Gnus' group parameter
(gcc-self . t) to put all my replies to personal mail in my personal
mail group, already marked as read. However, I also use (display .
[and (not expire) (not reply) (not killed)]) to limit my view to
personal mail I haven't gotten around to answering yet. This however
means I see my messages, since they are only marked read and not
reply/killed.

What's a nice way of not seeing messages from me unless I specifically
remove the limit? I can probably use gnus-summary-limit-to-author with
a prefix argument. Adding

 (dummy-variable (gnus-summary-limit-to-author "sacha@free.net.ph" t))

to the group parameters doesn't do what (gnus-summary-limit-to-author
"sacha@free.net.ph" t) does when eval'd in a summary buffer.

Would appreciate any tips. Probably has something to do with
gnus-summary-limit-to-display-predicate or what...

-- 
Sacha Chua <sacha@free.net.ph> - 4 BS CS Ateneo geekette
interests: emacs, gnu/linux, wearables, teaching compsci

Re: Marking replies that are gcc'd to the same group

[Lars Magne Ingebrigtsen]

Sacha Chua <sacha@free.net.ph> writes:

> What's a nice way of not seeing messages from me unless I specifically
> remove the limit? I can probably use gnus-summary-limit-to-author with
> a prefix argument. Adding
>
>  (dummy-variable (gnus-summary-limit-to-author "sacha@free.net.ph" t))
>
> to the group parameters doesn't do what (gnus-summary-limit-to-author
> "sacha@free.net.ph" t) does when eval'd in a summary buffer.

It's evaluated much too early.

I'd suggest calling that from a summary hook that's called late --
for instance `gnus-summary-prepare-hook'.

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen