unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: m43cap@yandex.com, 31737@debbugs.gnu.org
Subject: bug#31737: 26.1.50; Gnus does not use mailutils movemail
Date: Mon, 11 Jun 2018 18:20:12 +0300	[thread overview]
Message-ID: <83lgblqrir.fsf@gnu.org> (raw)
In-Reply-To: <871sddk9su.fsf@gmail.com> (message from Robert Pluim on Mon, 11 Jun 2018 10:27:13 +0200)

> From: Robert Pluim <rpluim@gmail.com>
> Cc: m43cap@yandex.com,  31737@debbugs.gnu.org
> Date: Mon, 11 Jun 2018 10:27:13 +0200
> 
> I think the current suggested fix is this:
> 
>  		       (append
>  			(list
>  			 (or mail-source-movemail-program
> -			     (expand-file-name "movemail" exec-directory))
> +			     "movemail"
>  			 nil errors nil from to)))))
>  	      (when (file-exists-p to)
>  		(set-file-modes to mail-source-default-file-modes))
> 
> That will work for people who have Mailutils installed in $PATH, and
> for those who donʼt it should use the exec-directory one.
> 
> The only issue is that people who install Mailutils after they've
> built emacs will now be switched to using the Mailutils movemail, with
> no indication that itʼs happened.

Which is what we want, I think, given the message output by
'configure'.

So I think we should install the above.





  reply	other threads:[~2018-06-11 15:20 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-06 19:23 bug#31737: 26.1.50; Gnus does not use mailutils movemail Robert Pluim
2018-06-06 19:47 ` Colin Baxter
2018-06-06 19:55   ` Robert Pluim
2018-06-08 15:33     ` Eli Zaretskii
2018-06-08 16:01       ` Robert Pluim
2018-06-08 18:15         ` Eli Zaretskii
2018-06-08 18:47           ` Robert Pluim
2018-06-08 19:20             ` Eli Zaretskii
2018-06-11  8:27               ` Robert Pluim
2018-06-11 15:20                 ` Eli Zaretskii [this message]
2018-06-11 21:47                   ` Robert Pluim
2018-06-12  2:29                     ` Eli Zaretskii
2018-06-12  6:12                       ` Colin Baxter
2018-06-12 14:41                         ` Eli Zaretskii
2018-06-12 18:24                           ` Lars Ingebrigtsen
2018-06-13 14:08                             ` Robert Pluim
2018-06-13 16:42                               ` Eli Zaretskii
2018-06-14 12:14                                 ` Robert Pluim
2018-06-14 13:04                                   ` Robert Pluim
2018-06-14 13:45                                   ` Eli Zaretskii
2018-06-14 14:37                                     ` Robert Pluim
2018-06-14 15:07                                       ` Eli Zaretskii
2018-06-14 22:54 ` Paul Eggert
2018-06-15  7:08   ` Eli Zaretskii
2018-06-15  7:42     ` Paul Eggert
2018-06-15 10:21       ` Colin Baxter
2018-06-15 11:19         ` Robert Pluim

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=83lgblqrir.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=31737@debbugs.gnu.org \
    --cc=m43cap@yandex.com \
    --cc=rpluim@gmail.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.
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).