From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: [patch] gnus.el::gnus-invalid-group-regexp - Support IMAP
Date: Thu, 21 Aug 2003 16:23:21 +0200 [thread overview]
Message-ID: <v965kr144m.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <iluy8xo6j6u.fsf@latte.josefsson.org>
On Thu, Aug 21 2003, Simon Josefsson wrote:
> Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:
>
>> On Tue, Aug 19 2003, Simon Josefsson wrote:
>>
>>> A potential problem may be if you create, e.g., a nnml or nnfolder
>>> group with the name containing '/'. Does it work? With Agent/Caching
>>> too? Does it do what users expect? With all
>>> nnmail-use-long-file-names settings? No problems with having two
>>> groups 'foo' and 'foo/bar'? Many questions.
[...]
>> - The problem that we were discussing was only the character `/' in
>> IMAP groups. I don't think it's a good idea to let the user create
>> _any_ invalid group, e.g. with [: `'\"] and even empty group names.
>
> All of those characters are valid in IMAP,
Okay, we can change the "(string-match "/" match)" part. But at least
empty or other group names, that will most probably fail when used in
Gnus groups (which chars?) sooner or later[1] should remain forbidden,
IMHO. If the user is absolutely sure, he can always customize
`gnus-invalid-group-regexp'.
> and since some IMAP servers export regular file systems ($HOME/), I
> think it is even likely that people have group names containing some
> of those characters.
I know that it exists, but I remembered some problems related to this,
e.g. with "Unerwünschte Nachrichten" (?).
> OTOH if we allow ':' the user is pretty much required to use a
> secondary select method for that group, otherwise it will confuse the
> Gnus group name functions.
Then we would have to move the checks from `gnus-read-group' to
`gnus-group-make-group' and check for back end and select method
there, I think.
> I.e., is 'nnimap:foo' the group 'nnimap:foo' on the primary method,
> or the group 'foo' on a secondary nnimap method? OTTH, I don't
> think we should try to forbid this too much, most people have nnimap
> as a secondary select method, and in that case things will work
> fine. A warning and a question seems safe enough.
Could you please change the wording of the warning appropriately?
Bye, Reiner.
[1] Will Gcc to a group containing `"' work? And the other issues you
mentioned previously (see quote at the top).
--
,,,
(o o)
---ooO-(_)-Ooo--- PGP key available via WWW http://rsteib.home.pages.de/
next prev parent reply other threads:[~2003-08-21 14:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-19 16:16 Jari Aalto+mail.linux
2003-08-19 17:21 ` Simon Josefsson
2003-08-20 17:14 ` Reiner Steib
2003-08-20 22:46 ` Simon Josefsson
2003-08-21 14:23 ` Reiner Steib [this message]
2003-08-22 0:50 ` Simon Josefsson
2003-08-22 16:07 ` Reiner Steib
2003-08-19 18:17 Jari Aalto+mail.linux
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=v965kr144m.fsf@marauder.physik.uni-ulm.de \
--to=4.uce.03.r.s@nurfuerspam.de \
--cc=reiner.steib@gmx.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).