From: gorkab@sanchez.com (Brian Gorka)
Cc: "'Felix Lee'" <flee@teleport.com>, "'ding@gnus.org'" <ding@gnus.org>
Subject: RE: q0.12: agent dir names
Date: Fri, 10 Oct 1997 12:19:55 -0400 [thread overview]
Message-ID: <c=US%a=_%p=Sanchez_Computer%l=OZ-971010161955Z-80024@oz.sanchez.com> (raw)
Let me take back one of those smacks...
in .gnus:
;; No Colons to Filenames
(setq nnheader-file-name-translation-alist
'((?: . ?_)))
right from the docs of nnheader-file-name-translation-alist
In fact, this is the default value for this variable on OS/2 and MS
Windows (phooey) systems.
So I shouldn't have to set it, but I did anyway...
Group:
8: nntp+news.zeno.com:zeno.support.superprint.standard.epson
Fetching headers for
nntp+news.zeno.com:zeno.support.superprint.standard.epson...
Creating directory: invalid argument,
d:/emacs/News/agent/nntp/news.zeno.com/nntp+news/zeno/com:zeno
note the nasty colon at the end.
>-----Original Message-----
>From: Kai Grossjohann [SMTP:grossjohann@charly.cs.uni-dortmund.de]
>Sent: Friday, October 10, 1997 10:24 AM
>To: Brian Gorka
>Cc: 'Felix Lee'; 'ding@gnus.org'
>Subject: Re: q0.12: agent dir names
>
>>>>>> On Fri, 10 Oct 1997, Brian Gorka said:
>
> Brian> This syntax also does strange things under NT Emacs. the :
> Brian> is the drive letter separator and illegal for use in a
> Brian> filename. Makes the agent worthless under NT/95.
>
>What about nnheader-file-name-translation-alist?
>
>kai
>--
>~/.signature: No such file or directory
next reply other threads:[~1997-10-10 16:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-10 16:19 Brian Gorka [this message]
1997-10-10 16:43 ` Kai Grossjohann
1997-10-12 22:02 ` Lars Magne Ingebrigtsen
-- strict thread matches above, loose matches on Subject: below --
1997-10-10 16:08 Brian Gorka
1997-10-10 13:31 Brian Gorka
1997-10-10 14:24 ` Kai Grossjohann
1997-10-10 4:19 Felix Lee
1997-10-10 9:46 ` Kai Grossjohann
1997-10-10 21:43 ` Felix Lee
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='c=US%a=_%p=Sanchez_Computer%l=OZ-971010161955Z-80024@oz.sanchez.com' \
--to=gorkab@sanchez.com \
--cc=ding@gnus.org \
--cc=flee@teleport.com \
/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).