Open taranlu-houzz opened 2 years ago
This is a known issue in Logseq, it should be fixed by Logseq Team, I noticed this issue for a long time, and I believe Logseq Team also know this, we can be patient to wait for it to be fixed later by Logseq Team 😃
If this is fixed, many actions of many plugins will be more fluent actually.
Even though it is not fixed as of today, there's a hack you can just press TAB and use vim shortcuts, it'll continue form where you left off
It should be fixed now after Logseq v0.6.7
It should be fixed now after Logseq v0.6.7
It's still not fixed, could you reopen the issue pls ?
It should be fixed now after Logseq v0.6.7
It's still not fixed, could you reopen the issue pls ?
OK, but I took a hour to check, but can not figure out why, so it may be hard to fix.
any updates on this guys? just wondering. cheers
+1, Even though it is not fixed as of today.
It remains unfixed.
+1. Do you know any workaround? The fact that I need to use a mouse to return the focus ruins all the benefits of vim =(
Problem
I am using this plugin along with your main vim plugin: https://github.com/vipzhicheng/logseq-plugin-vim-shortcuts. After editing a block, I use
:w
to get back to the mainlogseq
view, but it seems to lose focus on the block where I entered the vim editor (although it is still highlighted).Desired Solution
It would be great if entering/exiting the vim editor keeps the proper focus in the main
logseq
view, so that navigation controls continue to work.