From: Kevin Greiner <kevin.greiner@vignette.com>
Subject: Re: HEADS UP! Unplugged (agent) marks handling changed
Date: Wed, 29 Sep 2004 20:48:22 -0500 [thread overview]
Message-ID: <uvfdwttll.fsf@vignette.com> (raw)
In-Reply-To: <cjb9ol$h8s$1@sea.gmane.org>
Ralf Angeli <dev.null@iwi.uni-sb.de> writes:
> * Kevin Greiner (2004-09-28) writes:
>
>> Ralf Angeli <dev.null@iwi.uni-sb.de> writes:
>>
>>> * Kevin Greiner (2004-09-27) writes:
>>>
>>>> Great work. It looks like the problem is in the gnus-server-to-method
>>>> call in gnus-agent-synchronize-group-flags. Can you add a (debug)
>>>> expression to gnus-agent-synchronize-group-flags then try to
>>>> synchronize flags? What I'm trying to understand is why
>>>> gnus-server-to-method returned nil when passed "news.individual.net"
>>>> as an argument.
>>>
>>> `(gnus-server-to-method "news.individual.net")' doesn't return nil, it
>>> returns `("news.individual.net" nntp "news.individual.net")':
> [...]
>> Hmmm... I was actually interested in com.text.tex which you reported
>> on 25 Sept as returning null.
>
> Then you probably mean, why `gnus-get-info' returns nil.
>
> That's because `(intern-soft "comp.text.tex" gnus-newsrc-hashtb)'
> returns nil. `gnus-newsrc-hashtb' looks like
>
> [[...] 0 0 0 0 0 0 nntp+news\.individual\.net:comp\.text\.tex 0 [...]]
>
> So it seems that "comp.text.tex" doesn't match this.
>
> The variable `gnus-newsrc-alist' which is used to build
> `gnus-newsrc-hashtb' is set via the `(gnus-load ding-file)' call in
> the function `gnus-read-newsrc-el-file'. (BTW, there is a variable
> `gnus-newsrc-assoc' let-bound in this function which is never set, so
> this seems a bit useless.) And in ~/.newsrc.eld the groups are
> specified in the long form "nntp+news.individual.net:de.comp.text.tex".
>
> That means either the `gnus-get-info' call has to use the long form as
> its argument or the groups in the ~/.newsrc.eld file have to be
> specified with their short forms.
The problem is that gnus-get-info isn't consistent. Sometimes it
needs the full name other times the 'real' name. I've updated yet
again, please give it a try.
Kevin
next prev parent reply other threads:[~2004-09-30 1:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-25 6:17 Kevin Greiner
2004-09-25 10:21 ` Ralf Angeli
2004-09-25 23:33 ` Kevin Greiner
2004-09-26 11:42 ` Ralf Angeli
2004-09-26 14:47 ` Ralf Angeli
2004-09-27 5:14 ` Kevin Greiner
2004-09-27 14:48 ` Ralf Angeli
2004-09-27 23:28 ` Kevin Greiner
2004-09-28 9:11 ` Ralf Angeli
2004-09-30 1:48 ` Kevin Greiner [this message]
2004-09-30 13:26 ` Ralf Angeli
2004-09-30 18:06 ` test
2004-10-01 3:37 ` Kevin Greiner
2004-10-01 4:54 ` Solved ? (was: HEADS UP! Unplugged (agent) marks handling changed) Xavier Maillard
2004-10-01 8:03 ` HEADS UP! Unplugged (agent) marks handling changed Ralf Angeli
2004-10-01 9:16 ` Simon Josefsson
2004-10-01 20:26 ` Kevin Greiner
2004-10-02 8:56 ` Ralf Angeli
2004-10-02 9:34 ` test
2004-10-01 8:05 ` Display of quoted-printable (was: HEADS UP! Unplugged (agent) marks handling changed) Ralf Angeli
2004-10-01 9:30 ` Display of quoted-printable Katsumi Yamaoka
2004-10-01 9:50 ` Ralf Angeli
2004-09-25 16:33 ` HEADS UP! Unplugged (agent) marks handling changed Ralf Angeli
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=uvfdwttll.fsf@vignette.com \
--to=kevin.greiner@vignette.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).