|Subject:||bug#18133: Suppressing asynchronous command output|
|Date:||Mon, 26 Dec 2016 23:43:45 +0000|
>> It would be nice if the user only had to change one thing to enable hiding
>> the async output buffer until there is output. If we only added the
>> function to display-buffer--action-functio
n-custom-type, the user still hasThe type specification of ‘display-buffer-alist’ goes as:
>> to manually add the right buffer name pattern and the action to
> Yes, I meant to add a value that would handle "*Async Shell Output*"
> buffer like described above.
:type `(alist :key-type
(choice :tag "Condition"
(function :tag "Matcher function"))
This associates regexps/matcher functions with actions. How, in such a
specification, can I splice in a buffer name associated with a key
_without_ assigning that pair to the default of ‘display-buffer-alist’?
Maybe I'm missing some detail of the customization interface.
>> And how should ‘display-buffer’ know whether "there's some material" in
>> that buffer?
> That's up to Reuben, I thought he had this figured out already.
Whatever he figures out, it will affect the decision whether to display
the buffer initially.
|[Prev in Thread]||Current Thread||[Next in Thread]|