From: Nelson Jose dos Santos Ferreira <Nelson.Ferreira@inesc.pt>
Cc: ding@gnus.org
Subject: Re: Marking as already read when using gcc-self?
Date: 05 Jan 1999 01:56:19 +0000 [thread overview]
Message-ID: <2xogoeh48s.fsf@ccae-sv.inesc.pt> (raw)
In-Reply-To: Lloyd Zusman's message of "04 Jan 1999 18:42:17 -0500"
[-- Attachment #1: Type: text/plain, Size: 2468 bytes --]
On 04 Jan 1999 18:42:17 -0500, Lloyd Zusman (aka "Lloyd"),
regarding 'Re: Marking as already read when using gcc-self?', said:
Lloyd> 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.
Lloyd> Ah yes ... I found it. It only contained the string "Gcc" and not
Lloyd> "gcc-self", so I didn't find it in my previous search.
Lloyd> Well, I'll devote a little bit of my time to this task.
Maybe you want to start from where I left off.
The patch attach has the problem where it doesn't set the
mark as read if the summary buffer for the group is the
current one (defeating the gcc-self purpose, but making
other gcc as read ok). Maybe you can figure out what's wrong
with it. It applies cleanly to pgnus 0.69.
Lloyd> Perhaps Gcc could cause a special header to be inserted into its saved
Lloyd> messages, such as ...
Lloyd> X-Gnus-Gcc-Action: <what to do>
Lloyd> Where <what to do> might be `tick' or `mark read' or something
Lloyd> similar. This could be specified via some sort of option, such as ...
Lloyd> (defvar gnus-gcc-action "mark read"
Lloyd> "*Action to be taken when the message is Gcc'ed.
Lloyd> Could be `tick', `mark read', etc.")
Good! I think this can be easily accomodated to my code
provide someone more elisp/gnus knowledgeable will help
track the problem.
Lloyd> Then, when entering summary mode, some routine (which one? ... well,
Lloyd> I'll dig around and find it if no one can make a suggestion) could
Lloyd> then recognize this `X-Gnus-Gcc-Action' header and perform the
Lloyd> specified action.
Lloyd> Does this sound like a good approach? Before I start hacking, I'd
Lloyd> appreciate any feedback and opinions from those of you who are
Lloyd> familiar with this part of Gnus.
[...]
As you can see by the patch I hacked the gcc treatment in
the message sending part, which is a diferent approach from
yours.Note that yours will show the message you sent on the
group buffer until you enter the group.
Best regards,
Nelson
[-- Attachment #2: GCC Mark as read patch for pgnus --]
[-- Type: application/x-patch, Size: 2151 bytes --]
[-- Attachment #3: Type: text/plain, Size: 269 bytes --]
---
Nelson Jose dos Santos Ferreira | . . . | INESC/PT-Servicos
Systems Integrator | |. / / . | Lisbon,PORTUGAL
mailto:Nelson.Ferreira@inesc.pt |.||\| | / | Phone:+351 (1) 3100050
| .|<:/ \. | Fax :+351 (1) 3100008
next prev parent reply other threads:[~1999-01-05 1:56 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
1999-01-05 1:56 ` Nelson Jose dos Santos Ferreira [this message]
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=2xogoeh48s.fsf@ccae-sv.inesc.pt \
--to=nelson.ferreira@inesc.pt \
--cc=ding@gnus.org \
/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).