a bit more vim modes maybe?

[nospor]

Hi, I see to enter edit mode in query, I must press "i". Great, so like in VIM? If yes, then could be added a bit more vim movements like j/k etc? For people who barely use arrows this days :) Thank you

[wagnergerald]

What I want to add is that "d" is quite tricky, as it clears everything, not only the line.

[chiendo97]

Perhaps it would be more convenient to support $EDITOR. This way, I can swiftly edit the query without disrupting the default keyboard layout.

[Jake-Etherflow]

I had the same thought on Friday - I gotchu, keep an eye out for a PR soon. It's a lot of changes tho, so it'll need to be tested pretty thoroughly.

[Zaloog]

Made a starter for a VimTextArea a while back, which supports basic navigations and mode switching.
Maybe this helpful as a starter https://gist.github.com/Zaloog/afba1bb7a8172b5385ef9ff83b0e2e92

On hindsight, it might just be easier to suspend the app and open $EDITOR if its set.
Guess one has to write into temporary file and then on return read the file and update the TextArea field

[Jake-Etherflow]

PR created for a mostly full vim-mode experience. I added a command to toggle it on, with the default being the current editing mode so that users unfamiliar with vim bindings wouldn't be disrupted.

https://github.com/Maxteabag/sqlit/pull/34

[ranzig]

Perhaps it would be more convenient to support $EDITOR. This way, I can swiftly edit the query without disrupting the default keyboard layout.

This; though you'd need to implement a "break- out" key combo so you could pass commands to sqlit (like ^b in tmux) .

Glad this is a request already; I found it odd that there was so much vim-like keybind integration everywhere except right where you most expect it.

[Sidatii]

I feel the same about this great tool not supporting vim keybinds. It would be great since one of inspiration sources was lazydocker. I appreciate it man. Thanks again.

[Maxteabag]

Thanks for the interest. I’m currently experimenting with the best way to implement this properly.

A key focus is supporting Vim motions without affecting users who don’t want them. The tool is meant for fast database queries, not long editing sessions, but I still want the editor to be efficient for more involved queries.

Rather than recreating Vim or Neovim, the focus is on good integration with existing editors, alongside incremental improvements to the built-in query editor.

[Jake-Etherflow]

Agreed - that was the primary reason for not modifying the default mode of the editor and putting it behind a space command toggle. I understand the reasoning for closing it out. Perhaps at some point I'll push out a fully modular plugin to enable it, but I don't want to waste time on it if it's not in the roadmap or if it's not within the intention of the design.

[Maxteabag]

V1.2 added support for vim modes.
https://github.com/Maxteabag/sqlit/releases/tag/v1.2

Feedback welcome.