booperlv / nvim-gomove Goto Github PK

E431: Format error in tags file "/home/pedro/.local/share/nvim/site/pack/packer/start/nvim-gomove/doc/tags"
Before byte 704
E149: Sorry, no help for test

Block move right not working with cyrillic characters
Left, Down, Up - works perfectly

Set move_past_end_col = true, but it does not work any more.

If the call in the buffer can not be modified will appear a large number of error messages, simplify the message will be a little better

Thank you for your great work to this plugin, I tried this plugin and everything works well. Except that this plugin does not work with specific key mappings like 'noremap ; :' 'noremap : ;'. I would like to know if possible or necessary to fix this issue. It would not be difficult for me to change this habit, but it would be nice if this plugin could work together directly with my original configuration.

With romgrk/nvim-treesitter-context active, it seems that the view is reset to the top of the file after movement, possibly due to vim.fn.cursor function call in each movement function. Please see the attached demo below. Perhaps nvim_win_set_cursor may resolve this issue?

Basically let's say i have this code:

1:
2: function hello()
3: 	print("hello")
4: end

so if i use the keybind to move hello function up by 1 one line you will up with this:

1: function hello()
2: 	print("hello")
3: end
4:

I know I can achieve this with a block but this imo could be faster when you have ur cursor over hello and it will just move accordingly

Hi, I've just realised that <A-k> doesn't move the selected lines in visual mode up, but the other keybinds seem to work as intended for both modes.

This is a much missing feature on doing gaphical editing, ie with jbyuki/venn.nvim#12

As I understand it, the plugin only provides moves but the goal is to make things more complete.
Since unfortunately neovim does not offer such "simple" features, it would be great to provide them consistently.

Side question:
Do you plan to provide a command to activate and deactivate the plugin like how venn.nvim works (buffer specific enabling via command)? This would make integration with buffer-specific setups much simpler.

First of all, thank you for this beautiful plugin, I can't overstate how much I love watching my selection jump over folds when I shift it.

It would be amazing if it could shift closed folds themselves!
Vertical shifting is the most important, horizontal shifting and duplication support can be deferred for a later point.

Hi,

I've been using vim-move until now and this plugin seems to be a very good alternative to that. One feature that I like with vim-move is that you can just re-assign the identifier and not needing to manually include all the mapping in your config. For example, you can do let g:move_key_modifier = 'C' to use CTRL with h, j, k, l to move the lines.

I was wondering if something similar is possible with this plugin. And, if it's not, can you provide an example on how to map the default "smart" bindings to, say, CTRL instead of ALT. (so that CTRL, SHIFT would also do what ALT, SHIFT does by default)

And sorry if this is something that expert vim people can figure out, but I'm not that expert, so I'd appreciate the help 🙂

Here is a screen recording showing the issue:

Isn't it supposed to move the line because i am in visual mode, not visual block mode. Seems like nvim-gomove somehow changes it to visual block mode. Is this intended ? If so do guide on how to avoid this.

My config is same as the one given in README.md