From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: gnus-summary-move-article problem may be a .newsrc.eld problem.
Date: 01 Dec 1999 19:39:41 +0100 [thread overview]
Message-ID: <m3yabe33pu.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <81sdup$o82$1@quimby.gnus.org>
Rob Browning <rlb@cs.utexas.edu> writes:
> After poking around in the source and annotating a bunch of it with
> "message" statements, I got the impression that the problem might be
> that my newsrc.eld had some groups that looked like this,
>
> ("nnml+rlb:inbox"
> 2 (...)
> (nnml "rlb"
> (nnml-directory "~/.gnus/mail/incoming")
> (nnml-active-file "~/.gnus/mail/incoming/active")))
>
> ("nnml+rlb:gnucash"
> 2 (...)
> (nnml "rlb"
> (nnml-directory "~/.gnus/mail/incoming")
> (nnml-active-file "~/.gnus/mail/incoming/active")))
>
> and others that looked like this
>
> ("nnml+rlb:sw.g-wrap" 2 nil nil "nnml:rlb")
[...]
> One question I have is, is the "expanded" server format prohibited for
> groups with the same server? If not, then I suppose there's probably
> some other bug still lurking that I only masked.
It should not be -- Gnus uses `gnus-server-equal' to see whether two
servers are equal or not, and it should understand both formats.
What does
(gnus-server-equal
'(nnml "rlb"
(nnml-directory "~/.gnus/mail/incoming")
(nnml-active-file "~/.gnus/mail/incoming/active"))
"nnml:rlb")
evaluate to?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1999-12-01 18:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-19 8:10 Tracking down a gnus-summary-move-article problem Rob Browning
1999-11-28 23:25 ` gnus-summary-move-article problem may be a .newsrc.eld problem Rob Browning
1999-11-29 0:17 ` Simon Josefsson
1999-11-29 4:46 ` Rob Browning
[not found] ` <81sdup$o82$1@quimby.gnus.org>
1999-12-01 18:39 ` Lars Magne Ingebrigtsen [this message]
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=m3yabe33pu.fsf@quimbies.gnus.org \
--to=larsi@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).