Subject: Re: bug#18133: Suppressing asynchronous command output

From: Eli Zaretskii <[email-masked]>
Date: Wed, 21 Dec 2016 19:55:52 +0200

> From: Reuben Thomas <[email-masked]>
> Date: Mon, 19 Dec 2016 15:48:00 +0000
> 
> Attached, a patch for this bug.
> 
> It makes hiding the output buffer until there is output the default behavior; if the user wishes to get the old
> behavior back, then display-buffer-alist can be customized to remove the new default element.

I'm okay with adding this feature, but why turn it on by default right
away?  The original discussion of this bug says nothing about making
this the default behavior.  Perhaps it would be better to let users
use it first, and then turn it on by default if there's popular
demand?

Thanks.