From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: {gnus|nnmail}-use-long-filename[s] beahviour changed
Date: 09 May 2000 13:04:20 -0400 [thread overview]
Message-ID: <2nn1lz7izv.fsf@tiger.jia.vnet> (raw)
In-Reply-To: <yszk8h4w191.fsf@king.swox.se>
>>>>> "Linus" == Linus Nordberg <linus@swox.se> writes:
[...]
Linus> I can't reproduce it with gnus-5.8.6 and an empty
Linus> ~/.newsrc.eld, but with my current ~/.newsrc.eld, articles for
Linus> foo/bar ends up in the directory ~/Mail/foo_bar. This happens
Linus> both when I move the article manually using
Linus> gnus-summary-move-article and when I let GNUS split incoming
Linus> articles.
"/" is not supposed to be the separator for translating group names to
path names. Translating "/" to "_" is because of some strange group
names, especially those from nnslashdot (when gnus-agent covers
nnslashdot). In your case, you can use foo.bar, which ends up in the
directory ~/Mail/foo/bar.
Shenghuo
next prev parent reply other threads:[~2000-05-09 17:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-18 9:41 Linus Nordberg
2000-04-21 12:49 ` Lars Magne Ingebrigtsen
2000-05-09 8:56 ` Linus Nordberg
2000-05-09 17:04 ` Shenghuo ZHU [this message]
2000-05-10 10:52 ` Linus Nordberg
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=2nn1lz7izv.fsf@tiger.jia.vnet \
--to=zsh@cs.rochester.edu \
/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).