Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: Saving attachments with a leading dot
Date: Wed, 24 Sep 2003 17:48:03 +0200	[thread overview]
Message-ID: <v9d6dq5gss.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <m3eky7vzv7.fsf@defun.localdomain>

On Wed, Sep 24 2003, Jesper Harder wrote:

> RFC 2183 says:

> |    +    Sending the file to a pipe (e.g., "| sh").

Emacs happily created »| xless« when trying to save such an
attachment.  The content isn't sent to a pipe.

[...]
> Gnus doesn't prevent creating startup files.  We could:
>
> · Strip leading dots from file names, or
>
> · Set the default value of `mm-default-directory' to somewhere
>   (where?), so attachments aren't saved in ~.

If we take a different directory, we need to make sure it exists and
create it otherwise.  (Personally, I don't like programs that clutter
up my ~/ with new directories.)  Using `message-directory' (default:
"~/Mail/") could cause problems; at least if the file looks similar to
an mbox file: `nnfolder-directory' defaults to `message-directory'
therefore `nnfolder-generate-active-file' would create bogus groups.
Subdirs under ~/Mail could conflict e.g. with nnml, I guess.

How about only changing the default of
`mm-file-name-rewrite-functions' from `nil' to, say
`mm-file-name-rfc-2183'?  `mm-file-name-rfc-2183' could do the
replacements (or offer them?).

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo--- PGP key available via WWW   http://rsteib.home.pages.de/




  parent reply	other threads:[~2003-09-24 15:48 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-23 23:39 Jesper Harder
2003-09-24 10:38 ` Ted Zlatanov
2003-09-25  3:24   ` Jesper Harder
2003-09-25  4:22     ` Ted Zlatanov
2003-09-25  5:49       ` Jochen Küpper
2003-09-29  3:28         ` Jesper Harder
2003-10-02 18:07           ` Ted Zlatanov
2003-10-02 19:56             ` Jochen Küpper
2003-10-03  1:35             ` Jesper Harder
2003-10-03 14:04               ` Benjamin Riefenstahl
2003-10-02 18:10         ` Ted Zlatanov
2003-09-24 13:53 ` Benjamin Riefenstahl
2003-09-24 14:40   ` Ted Zlatanov
2003-09-24 15:11     ` Benjamin Riefenstahl
2003-09-24 16:03       ` Ted Zlatanov
2003-09-24 16:16         ` Benjamin Riefenstahl
2003-09-24 17:45           ` Ted Zlatanov
2003-09-24 15:48 ` Reiner Steib [this message]
2003-09-24 16:11   ` Benjamin Riefenstahl
2003-09-25 14:40     ` Reiner Steib
2003-09-25  3:23   ` Jesper Harder
2003-09-25  8:44 ` Hanak David
2003-09-29  3:20   ` Jesper Harder
2003-10-17 17:31     ` Lars Magne Ingebrigtsen
2003-10-18 16:43       ` Jesper Harder
2003-10-18 16:50         ` Lars Magne Ingebrigtsen
2003-10-18 20:04           ` Jesper Harder
2003-10-18 23:17           ` Jesper Harder
2003-10-19 11:14             ` Lars Magne Ingebrigtsen

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=v9d6dq5gss.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).