Gnus development mailing list
 help / color / mirror / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Norman Walsh <ndw@nwalsh.com>
Cc: ding@gnus.org
Subject: Re: Emacs 26.1 and movemail?
Date: Wed, 06 Jun 2018 16:22:35 +0200	[thread overview]
Message-ID: <871sdkm1uc.fsf@gmail.com> (raw)
In-Reply-To: <8736y0nhcc.fsf@nwalsh.com> (Norman Walsh's message of "Wed, 06 Jun 2018 09:02:27 -0500")

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

Norman Walsh <ndw@nwalsh.com> writes:

> Adam Sjøgren <asjo@koldfront.dk> writes:
>> Maybe the second item in this annotated list of changes in Emacs 26.1 is
>> related:
>>
>>  · https://www.masteringemacs.org/article/whats-new-in-emacs-26-1
>
> Yes, I understood why the problem arose; what isn’t clear is what part
> of gnus (or what part of some other bit of infrastructure that gnus
> relies upon) I need to change. Where does gnus get the “I’ll look in
> libexec/… for movemail” config from?

If the emacs youʼre using was built '--with-mailutils', then movemail
indeeed doesnʼt get installed in libexec. You can in that case specify
the path to the correct movemail binary by customizing

mail-source-movemail-program

to the full path.

The fact that Gnus doesnʼt detect this situation automatically the way
eg rmail does is arguably a bug in gnus.

Robert

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2018-06-06 14:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-04 21:58 Norman Walsh
2018-06-04 22:15 ` Adam Sjøgren
2018-06-06 14:02   ` Norman Walsh
2018-06-06 14:22     ` Robert Pluim [this message]
2018-06-06 14:32     ` Adam Sjøgren

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=871sdkm1uc.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=ding@gnus.org \
    --cc=ndw@nwalsh.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.
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).