Gnus development mailing list
 help / color / mirror / Atom feed
From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: Re: gnus-summary-normal-undownloaded-face
Date: Tue, 16 Dec 2003 13:16:50 -0600	[thread overview]
Message-ID: <usmjky3ml.fsf@xpediantsolutions.com> (raw)
In-Reply-To: <upteoelvp.fsf@boost-consulting.com>

David Abrahams <dave@boost-consulting.com> writes:

> Kevin Greiner <kgreiner@xpediantsolutions.com> writes:
>
>> David Abrahams <dave@boost-consulting.com> writes:
>>
>>> Ivan Boldyrev <boldyrev+nospam@cgitftp.uiggm.nsc.ru> writes:
>>>
>>>> On 8590 day of my life David Abrahams wrote:
>>>>> I'm sorry to be dense, but what I'm reading here isn't enough to tell
>>>>> me how to get my old behavior back.  The problem I'm having is that
>>>>> none of my new undownloaded articles are using any of the
>>>>> gnus-summary-xxx-undownloaded-faces; they look just like downloaded
>>>>> articles, except for the "." in the left column.
>>>>>
>>>>> What should I do?
>>
>> Well, the first question should be, do you have the agent enabled for
>> the particular group that you are viewing?  The absolute certain
>> answer is to open your summary buffer then evaluate the variable (c-h v)
>> gnus-newsgroup-agentized.  Its value will be non-nil when the agent is
>> enabled for this group.
>
> Apparently I don't, for some strange reason.  Why would that have
> changed when I updated my Gnus?

It probably changed because I rewrote the code that keeps track of the
agentized servers.  The old code used a server's method so any change
to your server configuration and a server could be de-agentized.
It's something that people have been complaining about for years.  In
the new code, the agent uses a unique name derived from the method.
The result is that you can make configuration changes without
effecting the agent.  The downside is that the backwards-compatibility
portion of the code isn't as reliable as I had thought.

You should be able to fix your problem by manually adding the server
to the agent.  Doing so will update agent/lib/servers to use the new
server names.

Kevin



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

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-10 12:06 gnus-summary-normal-undownloaded-face Per Abrahamsen
2003-12-10 13:21 ` gnus-summary-normal-undownloaded-face Per Abrahamsen
2003-12-10 14:31   ` gnus-summary-normal-undownloaded-face Reiner Steib
2003-12-12 13:27   ` gnus-summary-normal-undownloaded-face David Abrahams
2003-12-13  5:20     ` gnus-summary-normal-undownloaded-face Ivan Boldyrev
2003-12-13 15:40       ` gnus-summary-normal-undownloaded-face David Abrahams
2003-12-13 18:28         ` gnus-summary-normal-undownloaded-face Reiner Steib
2003-12-14 14:51         ` gnus-summary-normal-undownloaded-face Kevin Greiner
2003-12-16 17:02           ` gnus-summary-normal-undownloaded-face David Abrahams
2003-12-16 19:16             ` Kevin Greiner [this message]
2003-12-30 20:53           ` gnus-summary-normal-undownloaded-face Marcus Frings
2003-12-31  0:58             ` gnus-summary-normal-undownloaded-face Kevin Greiner
2004-01-02 19:21               ` gnus-summary-normal-undownloaded-face Marcus Frings
2004-01-03 16:35                 ` gnus-summary-normal-undownloaded-face Marcus Frings
2004-01-03 17:51                   ` gnus-summary-normal-undownloaded-face Reiner Steib
2004-01-03 18:54                   ` gnus-summary-normal-undownloaded-face Lars Magne Ingebrigtsen
2004-01-04  0:01                     ` gnus-summary-normal-undownloaded-face Marcus Frings
2004-01-08  0:43                     ` gnus-summary-normal-undownloaded-face Kevin Greiner
2004-01-08  0:47                   ` gnus-summary-normal-undownloaded-face Kevin Greiner
2004-01-10 21:41                     ` gnus-summary-normal-undownloaded-face Marcus Frings

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=usmjky3ml.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).