Gnus development mailing list
 help / color / mirror / Atom feed
From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: Re: Canonical list of marks with and without gnus-agent
Date: Mon, 12 May 2003 14:18:47 -0500	[thread overview]
Message-ID: <ur874j7mw.fsf@xpediantsolutions.com> (raw)
In-Reply-To: <u1c0yyog.fsf@asfast.com>

Lloyd Zusman <ljz@asfast.com> writes:

> Kevin Greiner <kgreiner@xpediantsolutions.com> writes:
>
>> Lloyd Zusman <ljz@asfast.com> writes:
>>
>>> Is there any documentation that has in one, single location the
>>> canonical list of marks that are defined when using gnus-agent, and when
>>> not using gnus-agent?
>>>
>>> Ideally, I'm looking for a 3-column list something like this:
>>>
>>>                      character used     character used            
>>>   Gnus mark name     with gnus-agent    without gnus-agent
>>
>> As far as I know, there are NO marks that change characters depending
>> upon use of the agent.
>>
>> The agent uses gnus-undownloaded-mark (-), gnus-downloaded-mark (+),
>> and gnus-downloadable-mark (%).  The two downloaded marks are stored
>> separately and displayed using their own format specifier (at least in
>> the later 5.9 series and now in 5.10) so I doubt that their of much
>> interest to you.  The gnus-downloadable-mark is the only one that
>> interacts with the other marks (i.e. ticked, read, etc).  
>
> Well, I'm glad that the marks are mostly the same between agent and
> non-agent mode.
>
> And yes, I've noticed that the '%' mark does indeed interact with
> ticked, read, etc.  I have some custom elisp that makes use of mark
> settings (ticked, read, etc.), and since I started agentizing, this code
> has broken.  That's what prompted me to post the previous message.
>
> So now I see that I need to understand this interaction between
> gnus-downloadable-mark and the others, but nothing in the docs talks
> about this interaction.
>
> Could someone either describe this interaction, or else point me to the
> location of an explanation?
>

All of the code is in gnus-sum.el but I don't think that will help.  The
downloadable mark is a manual mark.  If you haven't set it, it won't
be interferring with your code.  It might be better to simply post
your function then ask for comments.

Kevin



  reply	other threads:[~2003-05-12 19:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-12 11:09 Lloyd Zusman
2003-05-12 14:42 ` Kevin Greiner
2003-05-12 15:25   ` Lloyd Zusman
2003-05-12 19:18     ` Kevin Greiner [this message]
2003-05-14 14:00       ` Lloyd Zusman
2003-05-14 17:26         ` Kevin Greiner
2003-05-14 21:01           ` Lloyd Zusman
2003-05-15  5:29             ` Kevin Greiner
2003-05-15 13:23               ` Lloyd Zusman
2003-05-15 14:29                 ` Lloyd Zusman
2003-05-15 15:18                   ` Kevin Greiner
2003-05-14  5:01 ` Michael R. Wolf

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=ur874j7mw.fsf@xpediantsolutions.com \
    --to=kgreiner@xpediantsolutions.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).