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: 05 Jan 1999 19:53:57 -0500	[thread overview]
Message-ID: <ltpv8t1asa.fsf@asfast.com> (raw)
In-Reply-To: Nelson Jose dos Santos Ferreira's message of "05 Jan 1999 01:56:19 +0000"

Nelson Jose dos Santos Ferreira <Nelson.Ferreira@inesc.pt> writes:

> 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.

After realizing that the `X-Gnus-Gcc-Action' header isn't such a good
idea after all (others pointed out that people could send email or
news with that header set, thereby screwing up my newsreader), I took
a different approach, which seems to be similar to yours ... and
unfortunately, I hit the same problem that you did.  :(

But I'll keep plugging away ... and once I figure this out, I'll let
you know.

And thanks for the patch!

Sincerely,

- Lloyd

-- 
 Lloyd Zusman
 ljz@asfast.com


  reply	other threads:[~1999-01-06  0:53 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
1999-01-06  0:53       ` Lloyd Zusman [this message]
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=ltpv8t1asa.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).