unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Reitter <david.reitter@gmail.com>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
	Emacs-Devel devel <emacs-devel@gnu.org>
Subject: Re: send-mail-function / mailclient
Date: Tue, 27 Jan 2009 08:48:00 -0500	[thread overview]
Message-ID: <166979D5-3F91-4EA7-9470-6D6FDC63B15C@gmail.com> (raw)
In-Reply-To: <e01d8a50901201225x7ac109d9jd39c5e98ba3fa1d3@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1797 bytes --]

On 20 Jan 2009, at 15:25, Lennart Borgman wrote:

> When this was discussed some time ago a workaround was implemented for
> w32. I think this can be used on most platforms.
>
> With this workaround you can edit the data in both Emacs and the mail
> client. When you finish editing the mail message in Emacs the users
> mail client is started to edit a new mail message. This message has
> the subject from Emacs, but the body just says


That is a clean, working solution.  Any application that sends e-mail  
will have the problem of making users configure mail servers.  Thus, I  
would find it acceptable to use mailclient as default.  It would be  
important to point people to `send-mail-function' when they configure  
the mail servers (i.e. in the appropriate doc strings at least).   It  
is clear that mailclient makes no sense once somebody uses Emacs for  
mail...

Similarly, M-x report-emacs-bug wasn't conceived for such an  
arrangement:

>> - Buffers are edited twice - once in Emacs, and then again in the  
>> mail
>> client.  The mailto:// protocol wasn't designed to handle full  
>> messages to
>> be sent off without editing.  We're abusing the protocol.

Finally:

> - What happens if Emacs is used as mailto:// handler?  At least on my
> system, we don't provide the function directly, but in principle,  
> users
> should be able to do this.  If GNU/Linux has some kind of accepted  
> standard
> to announce "I can handle xxx:// URLs", then perhaps we should  
> implement it
> (for all systems).

Perhaps GNU/Linux doesn't offer a central way to advertise URL  
protocol handlers, but other systems do.  We need a way to set this in  
Emacs 23.2.


However, there seems to be a consensus that mailclient would be the  
right default on all systems now.  Is this agreed?

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 2193 bytes --]

      reply	other threads:[~2009-01-27 13:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-18 20:14 send-mail-function / mailclient David Reitter
2009-01-20  4:52 ` Stefan Monnier
2009-01-20 20:06   ` David Reitter
2009-01-20 20:25     ` Lennart Borgman
2009-01-27 13:48       ` David Reitter [this message]

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=166979D5-3F91-4EA7-9470-6D6FDC63B15C@gmail.com \
    --to=david.reitter@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=lennart.borgman@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    /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).