From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/53793 Path: main.gmane.org!not-for-mail From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de> Newsgroups: gmane.emacs.gnus.general Subject: Re: [patch] gnus.el::gnus-invalid-group-regexp - Support IMAP Date: Thu, 21 Aug 2003 16:23:21 +0200 Organization: Dept. of Theoretical Physics, University of Ulm Sender: ding-owner@lists.math.uh.edu Message-ID: References: Reply-To: reiner.steib@gmx.de NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: sea.gmane.org 1061476519 5434 80.91.224.253 (21 Aug 2003 14:35:19 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 21 Aug 2003 14:35:19 +0000 (UTC) Original-X-From: ding-owner+M2333@lists.math.uh.edu Thu Aug 21 16:35:17 2003 Return-path: Original-Received: from malifon.math.uh.edu ([129.7.128.13]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 19pqWx-0004zv-00 for ; Thu, 21 Aug 2003 16:35:17 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by malifon.math.uh.edu with smtp (Exim 3.20 #1) id 19pqSA-0003Uq-00; Thu, 21 Aug 2003 09:30:18 -0500 Original-Received: from sclp3.sclp.com ([64.157.176.121]) by malifon.math.uh.edu with smtp (Exim 3.20 #1) id 19pqS1-0003Ui-00 for ding@lists.math.uh.edu; Thu, 21 Aug 2003 09:30:09 -0500 Original-Received: (qmail 84698 invoked by alias); 21 Aug 2003 14:30:09 -0000 Original-Received: (qmail 84693 invoked from network); 21 Aug 2003 14:30:08 -0000 Original-Received: from main.gmane.org (80.91.224.249) by sclp3.sclp.com with SMTP; 21 Aug 2003 14:30:08 -0000 Original-Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 19pqSv-00011h-00 for ; Thu, 21 Aug 2003 16:31:05 +0200 Mail-Followup-To: ding@gnus.org X-Injected-Via-Gmane: http://gmane.org/ Original-To: ding@gnus.org Original-Received: from sea.gmane.org ([80.91.224.252]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 19pqSu-00011Z-00 for ; Thu, 21 Aug 2003 16:31:04 +0200 Original-Received: from news by sea.gmane.org with local (Exim 3.35 #1 (Debian)) id 19pqRx-0001EP-00 for ; Thu, 21 Aug 2003 16:30:05 +0200 Original-Lines: 55 Original-X-Complaints-To: usenet@sea.gmane.org X-Face: P05mdcZT&lL[-s2=mw~RsllZ0zZAb?vdE}.s 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/