> From: Edgar Vincent <e-v@posteo.net>> Date: Fri, 15 Sep 2023 11:35:35 +0000>> Hello Prot,
Hello Edgar,
> I am gently bringing my suggestion to your attention again. I do not> want to be pushy but simply wish to make sure this hasn't escaped your> attention.
I remember we discussed this before, but forgot what the outcome was. I
did not have regular access to the Internet in the meantime and so I am
still out of sync. If you can summarise the issue, it will be easier.
All the best,
Prot
--
Protesilaos Stavrou
https://protesilaos.com
Re: beframe: in Consult integration, return '(other-buffer)' first?
On 15/09/2023 14:07, Protesilaos Stavrou wrote:
> Hello Edgar,>> I remember we discussed this before, but forgot what the outcome was. I> did not have regular access to the Internet in the meantime and so I am> still out of sync. If you can summarise the issue, it will be easier.>> All the best,> Prot>
Certainly.
My suggestion was related to the default order of beframe buffers
in the context of its integration with Consult as described in the
README. If one follows the example in the README, the first buffer
in the list is the currently selected buffer, which I don't think is what
most users would expect. I think the first candidate should be
the previously selected buffer, similarly to how `beframe-switch-buffer'
behaves.
You'll find attached a patch providing an example of the suggested
changes.
Best,
Edgar
Re: beframe: in Consult integration, return '(other-buffer)' first?
> From: Edgar Vincent <e-v@posteo.net>> Date: Fri, 15 Sep 2023 15:08:23 +0000> [... 21 lines elided]> You'll find attached a patch providing an example of the suggested> changes.> [... 54 lines elided]
Thank you! I just made the changes and included your name in the
"Acknowledgements" section of the manual.
--
Protesilaos Stavrou
https://protesilaos.com