unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: mail-add-attachment
Date: Fri, 09 Sep 2011 10:32:19 -0400	[thread overview]
Message-ID: <jwv4o0liyh9.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <838vq60wm6.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 03 Sep 2011 13:05:21 +0300")

> Is it okay to install this command at this time?  I know we're in a
> feature freeze, but the new command is actually a very thin wrapper
> around code we already use elsewhere (gnus-dired.el and mml.el).  The
> result will be that users of sendmail.el will be able to send MIME
> attachments.  Here's the patch:

I guess it could be OK.
I have a few comments, tho:

> +(autoload 'mml-attach-file "mml"
> +  "Attach a file to the outgoing MIME message.
> +The file is not inserted or encoded until you send the message with
> +`\\[message-send-and-exit]' or `\\[message-send]'.
> +
> +FILE is the name of the file to attach.  TYPE is its
> +content-type, a string of the form \"type/subtype\".  DESCRIPTION
> +is a one-line description of the attachment.  The DISPOSITION
> +specifies how the attachment is intended to be displayed.  It can
> +be either \"inline\" (displayed automatically within the message
> +body) or \"attachment\" (separate from the body).")
> +
> +(autoload 'mm-default-file-encoding "mm-encode"
> +  "Return the default encoding for FILE.")

I must say I don't like such manually-managed autoloads.  I'd rather use
a declare-function plus an explicit require call.  My favorite would be
to use a new require-autoload construct which the byte-compiler would
replace by autoloads of the functions actually called (so the
byte-compiler would manage the list of autoloads rather than doing it by
hand).

> +\\[mail-attach-file] insert a text file into the message.
> +\\[mail-add-attachment] add to the message a file as a MIME attachment.

I think mail-attach-file needs to be renamed to mail-insert-file.


        Stefan



  parent reply	other threads:[~2011-09-09 14:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-03 10:05 mail-add-attachment Eli Zaretskii
2011-09-03 10:33 ` mail-add-attachment Andreas Schwab
2011-09-03 11:38   ` mail-add-attachment Eli Zaretskii
2011-09-03 11:54     ` mail-add-attachment Eli Zaretskii
2011-09-03 18:36       ` mail-add-attachment Chong Yidong
2011-09-08 16:38 ` mail-add-attachment Eli Zaretskii
2011-09-09 14:32 ` Stefan Monnier [this message]
2011-09-09 15:04   ` mail-add-attachment Eli Zaretskii
2011-09-09 16:15     ` mail-add-attachment Lars Magne Ingebrigtsen
2011-09-09 21:49     ` mail-add-attachment Stefan Monnier
2011-09-10  0:02       ` mail-add-attachment Lars Magne Ingebrigtsen
2011-09-10  1:40         ` mail-add-attachment Stefan Monnier
2011-09-10  8:32   ` mail-add-attachment Eli Zaretskii

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwv4o0liyh9.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).