[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#18133: Suppressing asynchronous command output
From: |
martin rudalics |
Subject: |
bug#18133: Suppressing asynchronous command output |
Date: |
Thu, 22 Dec 2016 18:53:47 +0100 |
>> 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?
>
> I think it could be. Martin, WDYT?
What is a toggleable option? A new action function? Or simply adding
‘display-buffer-no-window’ to the value menu? Or something completely
different?
martin
- bug#18133: Suppressing asynchronous command output, Reuben Thomas, 2016/12/19
- bug#18133: Suppressing asynchronous command output, Eli Zaretskii, 2016/12/21
- bug#18133: Suppressing asynchronous command output, Reuben Thomas, 2016/12/21
- bug#18133: Suppressing asynchronous command output, Eli Zaretskii, 2016/12/22
- bug#18133: Suppressing asynchronous command output,
martin rudalics <=
- bug#18133: Suppressing asynchronous command output, Eli Zaretskii, 2016/12/22
- bug#18133: Suppressing asynchronous command output, Reuben Thomas, 2016/12/22
- bug#18133: Suppressing asynchronous command output, martin rudalics, 2016/12/22
- bug#18133: Suppressing asynchronous command output, Reuben Thomas, 2016/12/22
- bug#18133: Suppressing asynchronous command output, martin rudalics, 2016/12/23
- bug#18133: Suppressing asynchronous command output, Reuben Thomas, 2016/12/23
- bug#18133: Suppressing asynchronous command output, martin rudalics, 2016/12/23
- bug#18133: Suppressing asynchronous command output, Reuben Thomas, 2016/12/23
- bug#18133: Suppressing asynchronous command output, martin rudalics, 2016/12/24
- bug#18133: Suppressing asynchronous command output, Reuben Thomas, 2016/12/24