GNU bug report logs -
#74361
[PATCH] New option xref-navigation-display-window-action
Previous Next
Full log
View this message in rfc822 format
>> >> 1. Demote these options to variables not intended for customization.
>> >> 2. Move their current default values to display-buffer calls.
>> >
>> > I expected to see us do #2 at the same time we deprecated the user
>> > options. I don't understand why we didn't do that. The deprecation
>> > message clearly tells users not to use these variables, so it's
>> > reasonable to expect them to be deleted. Moreover, their presence in
>> > our sources is a potential cause for byte-compilation warnings.
>>
>> Immediate #2 will break customization for many users.
>> We have to give enough time between two releases
>> to allow the users to see a warning and adapt their
>> config files to upcoming deletion of these options.
>
> But isn't it true that if users adapt their config files, the
> customization will stop working for them because category is not used
> by comint?
Adapting config files means replacing such settings
(setopt display-comint-buffer-action
'((display-buffer-same-window)
(inhibit-same-window . nil)))
with
(add-to-list 'display-buffer-alist
'((category . comint)
(display-buffer-same-window)
(inhibit-same-window . nil)))
This already works since all corresponding display-buffer calls
already provide the 'comint' category.
This bug report was last modified 172 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.