On Thu, Dec 20, 2018 at 02:47:51PM -0600, Derek Martin wrote:
You can also just set the hostname config variable in your muttrc, and
then it should skip the DNS lookup.
Actually the Hostname and Fqdn setting are done before any config files
are read in. I seem to recall there is some obscure
On Thu, Dec 20, 2018 at 10:05:30AM -0800, Kevin J. McCarthy wrote:
> On Thu, Dec 20, 2018 at 06:14:31PM +0900, Kenichi Asai wrote:
> >My guess is that mutt automatically checks some machine or network
> >configuration and wait 5 seconds for time out before starting. Does
> >mutt do such things?
I've seen this issue before on macOS. Specifically it happens if your
hostname has a dot. Here's an example program showing how long this can
take. https://gist.github.com/keith/86642ac3f695841b17906732c803fda3
I _believe_ I fixed this with:
`sudo scutil --set HostName name-without-dot`
--
On Thu, Dec 20, 2018 at 06:14:31PM +0900, Kenichi Asai wrote:
My guess is that mutt automatically checks some machine or network
configuration and wait 5 seconds for time out before starting. Does
mutt do such things? How can I learn about them?
In 1.6.0, mutt was changed to determine the
On 20181220, Kenichi Asai wrote:
> Why does it take so long time to start up? Have anybody had the same
> experience? What should I check?
Try starting it with "-d nnn" debugging; that might show you wh
Dear Mutt experts,
I am using mutt in the following configuration without any problems.
Mutt 1.9.0 (2017-09-02), installed via homebrew
macOS Sierra 10.12.6 on Mac mini (Late 2014)
However, when I cloned the entire hard drive (using DiskUtility) to
MacBookPro (Mid 2012), mutt takes about 5
