From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: Change request: remove "/" from gnus-invalid-group-regexp
Date: Tue, 16 Oct 2001 18:41:57 +0200 [thread overview]
Message-ID: <vaf8zeby1t6.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m38zebljcy.fsf@multivac.cwru.edu> (prj@po.cwru.edu's message of "Tue, 16 Oct 2001 11:00:55 -0400")
prj@po.cwru.edu (Paul Jarc) writes:
> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) wrote:
>>
>> I wonder if something bad happens if somebody creates an nnml group
>> with "/" in its name?
>
> The only obstacle, I think, is that if nnchoke-request-create-group
> returns nil, Gnus doesn't notice the error. nnmaildir already fails
> this way for group names it doesn't like.
Well, Gnus should notice whether nnchoke-request-create-group has
failed. Some mechanism should be designed and documented, and then
all backends should be changed to follow that design.
But what I was thinking about is more like that nnml.el converts dots
to slashes in the group name and then creates the right directory.
But that means you can have two names for the same group, which could
greatly confuse Gnus.
Right now, you can't have two names for the same group because "/" is
disallowed in group names.
Hm.
kai
--
Linux provides a nice `poweroff' command, but where is `poweron'?
next prev parent reply other threads:[~2001-10-16 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-16 13:05 Kai Großjohann
2001-10-16 15:00 ` Paul Jarc
2001-10-16 16:41 ` Kai Großjohann [this message]
2001-10-16 16:50 ` Paul Jarc
2001-10-16 18:59 ` Paul Jarc
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=vaf8zeby1t6.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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).