From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Protect against servers stepping on each other's toes
Date: Mon, 22 Oct 2001 22:05:20 +0200 [thread overview]
Message-ID: <vafn12j785b.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <87g08bwr7g.fsf@squeaker.lickey.com> (Matt Armstrong's message of "Mon, 22 Oct 2001 10:54:27 -0600")
Matt Armstrong <matt@lickey.com> writes:
> This is particularly dangerous because operations such as "B c" can
> cause select methods to magically appear. I wonder if this is wise.
Same for me. This has been discussed before.
> I also notice that if I gnus-server-regenerate-server my "nnml:"
> server, it gets confused by the Mail/archive directory (which is an
> nnfolder: thing by default, and is placed in Mail/ by default).
Right. I wish somebody found the time to implement the warnings that
we have discussed a few days ago.
> Have all these issues always been present? I think not. Hasn't
> Gnus historically only relied on .newsrc.eld for group info, and
> only recently looked at files on disk to try to find groups for the
> backends?
Yes, these issues have been present since day one. Astonishing that
there is now such a rush of bug reports about just this, right? But
it seems that's just the way it is. It was like that for me with
Tramp, too: for weeks, nothing, and then the same bug report N times.
kai
--
Lisp is kinda like tpircstsoP
next prev parent reply other threads:[~2001-10-22 20:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-19 21:35 Kai Großjohann
2001-10-19 21:49 ` Paul Jarc
2001-10-19 22:37 ` Kai Großjohann
2001-10-19 22:46 ` Paul Jarc
2001-10-20 11:00 ` Kai Großjohann
2001-10-20 6:48 ` Matt Armstrong
2001-10-20 11:03 ` Kai Großjohann
2001-10-20 21:49 ` Matt Armstrong
2001-10-20 22:02 ` Kai Großjohann
2001-10-22 5:35 ` Paul Jarc
2001-10-22 16:54 ` Matt Armstrong
2001-10-22 20:05 ` Kai Großjohann [this message]
2001-10-19 22:42 ` Simon Josefsson
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=vafn12j785b.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=ding@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).