On Sat, Aug 22, 2015 at 11:47 AM, Josef Fortier <josef.fortier@gmail.com> wrote:
My typical workflow with dbext:
1) Write a query
2) Visually select the block and execute the query (via <leader>se)
3) Go back to edit the query
repeat as needed.
However something in my usage pattern, or Dbext's selection logic, causes the cursor to jump to the end of the selection after executing the query. This introduces addition steps to return to where I was to edit the query.
Not your usage pattern, this is intentional (though I can't remember why).
I am putting the cursor at the end of the visual selection when I yank it. Vim itself puts the cursor back at the start of the visual selection if you hit y to yank the visually selected region.
Further, due to the vsp call, the cursor is often well past the query, which can sometimes trigger my inadvertently ending up on the next block.
I'd intuitively expect the cursor to remain where it was prior to execution, after returning.
For visual selections, that means the cursor is either at the start of the selection or the end of the selection
Is there some setting in dbext to turn this behavior off?
No setting for this.
I can send you a updated file to return the cursor to the start of the visual selection. And you can try it out for a bit.
David
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment