Gnus development mailing list
 help / color / mirror / Atom feed
From: Toby Speight <streapadair@gmx.net>
Subject: Re: moving mail from nnml -> nnimap
Date: 20 Jun 2000 13:10:21 +0100	[thread overview]
Message-ID: <uvgz4imdu.fsf@lanber.cam.eu.citrix.com> (raw)
In-Reply-To: Simon Josefsson's message of "19 Jun 2000 20:04:38 +0200"

Simon> Simon Josefsson <URL:mailto:simon@josefsson.org>

0> In article <m23dm9sg21.fsf@angelica.rsasecurity.com>,
0> Simon wrote:

Simon> Soren Dayton <dayton@overx.com> writes:

>> what do people do about the change is group hierarchy seperator?
>> Exchange uses "foo/bar" where gnus uses "foo.bar".  I just have to
>> do the translation myself because Exchange is more promiscuous
>> about names than gnus?  Is that the solution?
>> 
>> I see that gnus doesn't support making groups with "/" in the
>> names.  What have people done here?

Simon> Used group names with `/' names in them anyway. :-)
Simon>
Simon> I patched my version of `gnus-read-group' to allow `/' in group
Simon> names, and haven't noticed any problems.  I guess there might
Simon> be problems with backends other than nnimap, and that's the
Simon> reasons for the limit in valid characters.

I just subscribed my groups from browsing the server - I wasn't even
aware that Gnus didn't like the '/' (I've had no problems with spaces,
either).  My new groups were all created by splitting, so I've had no
problems there, either.




  parent reply	other threads:[~2000-06-20 12:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-19 14:11 Soren Dayton
2000-06-19 14:44 ` Kai Großjohann
2000-06-19 16:31   ` Soren Dayton
2000-06-19 18:04     ` Simon Josefsson
2000-06-19 21:12       ` Soren Dayton
2000-06-20 12:10       ` Toby Speight [this message]
2000-06-19 18:10     ` Kai Großjohann

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=uvgz4imdu.fsf@lanber.cam.eu.citrix.com \
    --to=streapadair@gmx.net \
    /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).