[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#18133: Suppressing asynchronous command output

From: Reuben Thomas
Subject: bug#18133: Suppressing asynchronous command output
Date: Wed, 21 Dec 2016 22:44:33 +0000

On 21 December 2016 at 17:55, Eli Zaretskii <address@hidden> wrote:
> From: Reuben Thomas <address@hidden>
> 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

Would a reasonable way to do this be to add a toggleable option to the defcustom for display-buffer-alist, and document this in async-shell-command's docstring?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]