Gnus development mailing list
 help / color / mirror / Atom feed
From: Lloyd Zusman <ljz@asfast.com>
Subject: Re: Marking as already read when using gcc-self?
Date: 04 Jan 1999 18:42:17 -0500	[thread overview]
Message-ID: <lt90fivc4m.fsf@asfast.com> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "04 Jan 1999 10:28:58 +0100"

Kai.Grossjohann@CS.Uni-Dortmund.DE writes:

> Lloyd Zusman <ljz@asfast.com> writes:
> 
>   > If I set the `gcc-self' group parameter for a given group to `t', is
>   > there any way to cause any messages that are archived into that group
>   > via this method to automatically be marked as `read' as soon as they
>   > appear in the group?
> 
> This is in the todo list.  See the node `Newest Features' in the Gnus
> info file.

Ah yes ... I found it.  It only contained the string "Gcc" and not
"gcc-self", so I didn't find it in my previous search.

Well, I'll devote a little bit of my time to this task.

Perhaps Gcc could cause a special header to be inserted into its saved
messages, such as ...

  X-Gnus-Gcc-Action: <what to do>

Where <what to do> might be `tick' or `mark read' or something
similar.  This could be specified via some sort of option, such as ...

  (defvar gnus-gcc-action "mark read"
   "*Action to be taken when the message is Gcc'ed.
   Could be `tick', `mark read', etc.")

Then, when entering summary mode, some routine (which one? ... well,
I'll dig around and find it if no one can make a suggestion) could
then recognize this `X-Gnus-Gcc-Action' header and perform the
specified action.

Does this sound like a good approach?  Before I start hacking, I'd
appreciate any feedback and opinions from those of you who are
familiar with this part of Gnus.

Thanks in advance.

-- 
 Lloyd Zusman
 ljz@asfast.com


  reply	other threads:[~1999-01-04 23:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-01-03  5:07 Lloyd Zusman
1999-01-04  9:28 ` Kai.Grossjohann
1999-01-04 23:42   ` Lloyd Zusman [this message]
1999-01-05  1:56     ` Nelson Jose dos Santos Ferreira
1999-01-06  0:53       ` Lloyd Zusman
1999-01-05  9:37     ` Stefan Waldherr
1999-01-05 12:44       ` Hrvoje Niksic
1999-01-06  4:45       ` Matt Simmons
1999-01-05 16:00     ` Justin Sheehy
1999-01-05 16:53       ` Hrvoje Niksic
1999-01-05 23:45         ` Lloyd Zusman
1999-01-06  7:41       ` Stefan Waldherr
1999-01-05 22:14     ` Kai.Grossjohann

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=lt90fivc4m.fsf@asfast.com \
    --to=ljz@asfast.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).