[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Allow controlling the effect of visibility on buffer switching
From: |
Eli Zaretskii |
Subject: |
Re: Allow controlling the effect of visibility on buffer switching |
Date: |
Wed, 26 Jan 2022 15:30:52 +0200 |
> From: Thuna <thuna.cing@gmail.com>
> Date: Wed, 26 Jan 2022 12:10:38 +0300
>
> Currently `read-buffer-to-switch' defaults to non-visible buffers. An
> option to control this behavior could be introduced as follows (a
> proof-of-concept, subject to change):
Thanks, but why do we need such an option, given that we have
buffer-change history, and so the visible buffers are usually just a
couple of keystrokes away, like M-n?
- Allow controlling the effect of visibility on buffer switching, Thuna, 2022/01/26
- Re: Allow controlling the effect of visibility on buffer switching,
Eli Zaretskii <=
- Re: Allow controlling the effect of visibility on buffer switching, Thuna, 2022/01/26
- Re: Allow controlling the effect of visibility on buffer switching, Michael Welsh Duggan, 2022/01/26
- Re: Allow controlling the effect of visibility on buffer switching, Juri Linkov, 2022/01/27
- Re: Allow controlling the effect of visibility on buffer switching, Thuna, 2022/01/29
- Re: Allow controlling the effect of visibility on buffer switching, Eli Zaretskii, 2022/01/29
- Re: Allow controlling the effect of visibility on buffer switching, Thuna, 2022/01/29
- Re: Allow controlling the effect of visibility on buffer switching, Po Lu, 2022/01/29