Bug 244859 - mail/neomutt: "press any key ..." message on startup
Summary: mail/neomutt: "press any key ..." message on startup
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Baptiste Daroussin
URL: https://github.com/neomutt/neomutt/is...
Keywords:
Depends on:
Blocks:
 
Reported: 2020-03-17 11:02 UTC by Michael Büker
Modified: 2020-03-24 16:58 UTC (History)
0 users

See Also:
bugzilla: maintainer-feedback? (bapt)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Büker 2020-03-17 11:02:33 UTC 
Since updating from 20191207 to 20200313, a "Press any key to continue ..." interruption appears on every startup of neomutt, regardless of configuration.
Comment 1 Michael Büker 2020-03-17 15:18:15 UTC 
Logging with `neomutt -d1` has uncovered the cause:

1) the neomutt config option "crypt_use_gpgme" defaults to yes (see neomutt -D)
2) my installation is compiled without gpgme support (see neomutt -v)

If these two collide, neomutt pauses at startup and asks to "Press any key to continue ..."

I guess on that screen it should be showing the actual error message:
'"crypt_use_gpgme" set but not built with GPGME support'
But apparently, the screen is cleared, erasing the message. In effect, only "Press any key to continue ..." is left on screen.

neomutt *does* show the error message as expected when running just `neomutt -D`.
Comment 2 Michael Büker 2020-03-17 16:10:26 UTC 
Apparently, this has been noticed and fixed upstream, next update should eliminate the problem.
Comment 3 Baptiste Daroussin freebsd_committer freebsd_triage 2020-03-24 16:58:23 UTC 
I have updated the port, so it should be fixed now.