Vertical delete in IdeaVIM - vim

In my normal VIM installation, I can select vertically with ctrl+v, move down and over however many lines, and then hit x to delete everything I've highlighted.
In IdeaVIM, doing the same thing only deletes the single character that I am highlighting with my cursor at the time.
Does anyone know how to change the IdeaVIM behavior to the regular VIM behavior?

This is fixed in IdeaVIM version 0.36, released 2014-10-14. The bug is tracked in VIM-632. Note off-by-one error tracked in VIM-501 is fixed in an upcoming release (probably will be called 0.38).

Related

VIM 8.2 Backspace Delete behavior

I uninstalled vim 8.1 which is the available version through my package manager and installed 8.2 from source. But Backspace and Delete buttons behave in a different way in this version.
If you are in insert mode and press Backspace then it does not delete or move indentation to the left. Delete button in insert mode deletes up to the end of the current line and does not continue to the next one.
Why these changes in behavior and how do I revert to the previous one?
I looked at the docs. You need to set:
set backspace=indent,eol,start
My previous installation was vim-gtk. I suppose this package has this value set as default.
Now both backspace and delete work as before.

The ý character in INSERT mode isn't printed

Issue description
I use VIM to take notes in Czech at university lectures. All special characters work fine except for the 'ý' character.
When I type it in INSERT mode, it isn't printed. Instead, it shifts the cursor to the left, which is very annoying.
The character is represented correctly when typed in the vim command line. So I suppose the character is misinterpreted as an INSERT mode movement command? Is this a bug?
How to reproduce
Please temporarily install the Czech QWERTZ keyboard layout (careful, there is a programmer version of the layout, we need the regular one).
Typing the 'ý' character can be accomplished using either of these steps:
The top number row is reserved for the most common special characters, press 7 without SHIFT to print it.
Special characters can also be typed by first pressing and then letting go the '=' key (next to BACKSPACE) and then pressing the character you want to decorate with an accent.
Wrapping up
Issue replication times: always
Ubuntu 17.10
Terminal
GUI vim-gnome
Bash on Ubuntu for Win 10
Running vim without vimrc solves the issue.
Link to my vimrc
Any suggestion and/or workaround will be very helpful.
Thanks in advance!
I know this is an older issue, but to anyone else struggling with this, it is an issue within the auto-pairs plugin, that has since gone silent and unmaintained. There's an issue for it.
If you don't want to scroll through the discussion, there's a fork of the plugin at https://github.com/lunarWatcher/auto-pairs which has the issue fixed. Since the original plugin is unmaintained, there's little hope of the fix being merged back, but I managed to switch to the fork with no apparent issues.
Přeji příjemné psaní ypsilonů s čárkou!
The abbreviation:
iabbrev 'y ý
could be used to display the ý character in insert mode. Typing 'y should result in ý.

Why does vim sometimes display linebreaks incorrectly?

I have a long line of text in vim, soft-wrap is on, I've done :set linebreak, and breakat has the right value.
The problem is, when I edit some text in the middle of the "paragraph", the lines don't wrap at word boundaries anymore.
Example:
1) Cursor is in the middle of the line:
2) I type cw and the linebreaks change:
It stays like that when I go back to normal mode, but wraps correctly again when the cursor leaves the line.
This does not happen if I add text in the middle, or do a command like dw - seemingly just commands that delete some text and enter insert mode.
The problem began on a fresh install of Fedora 21, but my .vimrc is unchanged from my previous computer, where I did not have this problem.
How do I restore the correct behavior, or is this perhaps a bug in the Fedora package?
I believe, this is a bug, that has been fixed with 7.4.576

Vim langmap breaks plugin (bépo)

I am using a bépo keymap (http://bepo.fr) and seeking the perfect vim mapping.
So far I used a long list of noremap, but for many binding (for exemple, the motion aw or Ctrl+r), the first keystroke is well remaped but not the others, I reckon it's the expected behaviour, but then this is not what I need.
Ideally I would have my keyboard totally remaped in a higher level (before the map commands) except when typing text (in insertion mode and when typing a substitution for exemple). What I'm looking for seems to be langmap, but I have problems using it.
I added this langmap to my .vimrc, It seems perfect but it broke some of my plugins. SuperTab now insert <Plug>SuperTabForward when pressing Tab in insertion mode, I have t<SNR>24_SelectCompletion(1) when pressing enter.
Does someone know how to fix this langmap issue or a better way to remap my keyboard?
This is a known bug, that has been discussed before. I have made a patch (see the thread starting here) and hopefully Bram will include this change soon.
Update 11/05/2014
This has been fixed by patch 7.4.502. Use the langnoremap option to fix this.

Down key behaviour when tabbing in Komodo Edit 7

I recently upgraded to Komodo Edit 7 from v6. In previous versions if I was adding tabs to the beginning of lines I could press down and the cursor would automatically move to the beginning of the next line. The net effect meant that to indent a whole bunch of line I just had to press DOWN and TAB repeatedly
Since I've upgraded it no longer works like this. If I press TAB at the beginning of a line and then down, it indents the first line, then moves to the next line, one tab width in.
Does anyone know how to re-enable this functionality on Komodo Edit 7, or whether it was completely removed?
I am experiencing the same issue. As Paul Sweatte suggests, there is an alternate way to indent a group of lines (adding tabs at the beginning), but no alternative exists for doing this in the middle of a group of lines.
I have submitted a bug here: http://bugs.activestate.com/show_bug.cgi?id=94104
Update: Bug status has been updated to Resolved. This should be fixed in the next release (7.1.0) or you can download the nightly build: http://downloads.activestate.com/Komodo/nightly/

Resources