unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jeff Clough <jeff@chaosphere.com>
To: <christian.lynbech@tieto.com>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: mailclient-send-it usage of browse-url
Date: Wed, 14 Apr 2010 09:36:34 -0400	[thread overview]
Message-ID: <m3wrwaw3z1.fsf@logrus.localdomain> (raw)
In-Reply-To: <ytqpbpdmb2s4.fsf@tieto.com> (christian lynbech's message of "Wed, 14 Apr 2010 15:07:55 +0200")

<christian.lynbech@tieto.com> writes:

>>>>>> "Jeff" == Jeff Clough <jeff@chaosphere.com> writes:
>
> Jeff> The problem is that there is not one universal way to ask an operating
> Jeff> system "How do I send a mail message?" and get an honest answer.  Under
> Jeff> Unix, you have tools like sendmail that are virtually guaranteed to be
> Jeff> there.  Under Windows, the Mac and other systems, not so much.
>
> I do not about Windows, but on Mac you can (I believe) rely on the
> *presence* of sendmail just as much as on other UNIX like systems.

With Windows your options are mailclient-send-it and hope for the best
or configure smtpmail-send-it to work.  (This is one item on a very long
list of things that caused my most recent move back to Linux.)

> First of all you somehow need to set up browse-url. If it works out of
> the box, it only does so because somebody took the time to figure what
> the default should be on a Mac. In fact, looking at the default setup
> for browse-url on emacs23 , it does not seem to be working out of the
> box on a Mac. "browse-url.el" will search for a number of programs such
> as firefox or konqueror but not Safari (which is all you can rely on on
> a Mac) and if you do not have any of the browsers in your path (perhaps
> because you use some desktop environment menu rather than setting up
> path), it fails. If you are using emacs-w3m which I think is a quite
> reasonable thing to do, the mailto: hack fails.

It does seem lame that it's not looking for Safari, but then I don't
know if it looks for IE on Windows.  This may be a philosophical point
and not a technical one, so for better or worse it just might not
happen.

> Secondly, browse-url is a user command and while few people may be as
> multi-frame-frenzied as me, there is none the less a significant risk
> that the user has tampered with the command.

I think a case can be made that tampering with a browser-oriented thing
shouldn't break an email-oriented thing when it is not obvious to the
end user that that's what's going to happen.  A case could also be made
that if one knows how to tamper with browse-url, they know how to
configure smtp mail correctly.

> My point is that using `browse-url' is a brittle foundation for an
> otherwise clever hack. 

I don't think this is so much that browse-url is brittle, just that a
case can be made that it should work for the more defaulty browsers.
The overall issue of having Emacs get the right answer to "What is your
mail client?" might still ought to be addressed in a way that doesn't
rely on browsers at all, which may be more possible now than it was
however long ago.

Jeff





  parent reply	other threads:[~2010-04-14 13:36 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-13 19:51 mailclient-send-it usage of browse-url Christian Lynbech
2010-04-13 22:06 ` David Reitter
2010-04-14  3:22   ` Christian Lynbech
2010-04-14 11:41     ` Jeff Clough
2010-04-14 13:07       ` christian.lynbech
2010-04-14 13:25         ` David Reitter
2010-04-15  7:46           ` christian.lynbech
     [not found]             ` <C8D541C4-F87C-48F8-917C-5A4C6AC02203@mit.edu>
2010-04-15 16:49               ` chad
2010-04-14 13:36         ` Jeff Clough [this message]
2010-04-14 16:02           ` David Reitter
2010-04-14 16:35             ` Chad Brown
2010-04-14 16:41             ` Jeff Clough
2010-04-14 17:46               ` David Reitter
2010-04-14 23:19                 ` Lennart Borgman
2010-04-15  2:28                 ` Stephen J. Turnbull
2010-04-15  7:52                   ` christian.lynbech
2010-04-15 17:13                     ` Stephen J. Turnbull
2010-04-15 18:48                     ` Richard Stallman
2010-04-16  8:05                       ` christian.lynbech
2010-04-17 19:55                         ` Richard Stallman
2010-04-14 19:58           ` David De La Harpe Golden
2010-04-14 14:23         ` Stefan Monnier
2010-04-15  8:14           ` christian.lynbech
2010-04-14 12:55     ` David Reitter
2010-04-14 13:20       ` christian.lynbech
2010-04-14 13:30         ` David Reitter
     [not found] <D6FDF877-2199-48E7-8B06-4E6325EDEAC9@mit.edu>
2010-04-15 16:49 ` Fwd: " chad
2010-04-15 17:15   ` Lennart Borgman
2010-04-15 17:22     ` Chad Brown
2010-04-15 19:00       ` Lennart Borgman
2010-04-16  0:14     ` Stefan Monnier
2010-04-16  0:34       ` Lennart Borgman
2010-04-16  1:08         ` Stefan Monnier
2010-04-16 11:13           ` Lennart Borgman
2010-04-16 12:49             ` Stefan Monnier

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=m3wrwaw3z1.fsf@logrus.localdomain \
    --to=jeff@chaosphere.com \
    --cc=christian.lynbech@tieto.com \
    --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).