[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#40919: 27.0.91; next-error-select-buffer does not always behave as d
From: |
Juri Linkov |
Subject: |
bug#40919: 27.0.91; next-error-select-buffer does not always behave as documented |
Date: |
Mon, 15 Jun 2020 02:15:30 +0300 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (x86_64-pc-linux-gnu) |
>>> what kind of functions do they want to put on there?
>> Both next-error-buffer-on-selected-frame and
>> next-error-no-navigation-try-current.
>>
>>> And/or would they be content to advice-add on
>>> next-error-find-buffer-function instead?
>> Is it possible to add advice-add by using customization?
>
> No, or at least not yet. But if we know of only one user that wants this
> setup, surely that's not a problem?
It's a general problem that hindered the development of other features
that might benefit from customizable advice-add (namely set-multi-message).
> By the way, you were going to evaluate the new default. Do you now think
> that it's problematic somehow (and, for instance, the previous was a
> better default), or do you want to change it as a purely
> personal preference?
Only personal preference, it seems the default in master is fine
for most users.
>>>> ;; 2. If next-error-last-buffer is an acceptable buffer, use that.
>>>> (if (and next-error-last-buffer
>>>> (next-error-buffer-p next-error-last-buffer avoid-current
>>>
>>> Should we take the rest of the cases in next-error-find-buffer and move
>>> them to the default value of the above hook?
>> I don't think so, I don't believe someone might want to customize the
>> rest of the cases.
>
> Well, if you're sure about that.
>
> Having them all on the hook seemed logical to me, but indeed I don't know
> how necessary that is.
The reason why I think no one might want to customize the rest of the cases
is because I believe that next-error-last-buffer is always non-nil, so
all other cases (i.e. 3, 4, 5, 6) are useless and never used. Isn't it so?
- bug#40919: 27.0.91; next-error-select-buffer does not always behave as documented, Juri Linkov, 2020/06/01
- bug#40919: 27.0.91; next-error-select-buffer does not always behave as documented, Dmitry Gutov, 2020/06/01
- bug#40919: 27.0.91; next-error-select-buffer does not always behave as documented, Juri Linkov, 2020/06/10
- bug#40919: 27.0.91; next-error-select-buffer does not always behave as documented, Dmitry Gutov, 2020/06/10
- bug#40919: 27.0.91; next-error-select-buffer does not always behave as documented, Juri Linkov, 2020/06/11
- bug#40919: 27.0.91; next-error-select-buffer does not always behave as documented, Dmitry Gutov, 2020/06/14
- bug#40919: 27.0.91; next-error-select-buffer does not always behave as documented,
Juri Linkov <=
- bug#40919: 27.0.91; next-error-select-buffer does not always behave as documented, Dmitry Gutov, 2020/06/15
- bug#40919: 27.0.91; next-error-select-buffer does not always behave as documented, Juri Linkov, 2020/06/24
- bug#40919: 27.0.91; next-error-select-buffer does not always behave as documented, Juri Linkov, 2020/06/10
- bug#40919: 27.0.91; next-error-select-buffer does not always behave as documented, Dmitry Gutov, 2020/06/10
- bug#40919: 27.0.91; next-error-select-buffer does not always behave as documented, Eli Zaretskii, 2020/06/11
- bug#40919: 27.0.91; next-error-select-buffer does not always behave as documented, Juri Linkov, 2020/06/11
- bug#40919: 27.0.91; next-error-select-buffer does not always behave as documented, Eli Zaretskii, 2020/06/12
- bug#40919: 27.0.91; next-error-select-buffer does not always behave as documented, Juri Linkov, 2020/06/13
- bug#40919: 27.0.91; next-error-select-buffer does not always behave as documented, Juri Linkov, 2020/06/14