74th / vscode-vim Goto Github PK

They call actions of VSCode and other plugins.

I'm used to using both w and e for movement, so it's a bit inconvenient for me right now when e is missing.

Given this code:

{
    "vimStyle.showMode": true
}

Using cw on true will change the text to this:

{
    "vimStyle.showMode": }

There is one small issue I have found so far:

When I am on line 6, and the file totals only 15 lines, if I do:20j then it should still round 20 down to 15 and subsequently go to line 15. Currently, you must give it an exact number, 9j in this case, to reach down to line 15.

Hi, tks for you plugin,but ...
workbench.main.js:1602 [Plugin Host] Cannot read property 'length' of undefined
workbench.main.js:1602 [Plugin Host] Object {}

push w

before:
fmt.Print("hello world")
   ^
except:
fmt.Print("hello world")
    ^
actual:
fmt.Print("hello world")
         ^

Enable using vim modes for keybidings.
ex:

{
    // Ctrl-H : BackSpace
    "key": "ctrl+h",
    "command": "deleteLeft",
    "when": "editorTextFocus && vim.inInsertMode"
},

And only enabled ESC keybindings to the option to enable vim extension.

{
    "command": "vim.Esc",
    "key": "escape",
    "when": "editorTextFocus && vim.enabled"
}

There are a few motion commands that do not seem to work in visual mode:

• arrow keys
• most word motions (e E w W b B …) only w and B seem to work
• others?

The arrow keys make the visual selection disappear, but the status bar still says VISUAL and pressing any Vim motion key restores it.

Any reason why 'u' isn't supported for undo?

Hey is it cool if I clean up some of your code?
It seems like you have interfaces all over the place which could be moved to a typings file (.d.ts)

After updating to the latest VS Code version with the latest release of vscode-vim, search acts like it can't find my text. It highlights them as I type, but will not iterate through what it finds.

Thank you for this plugin.

Only thing missing which I had come to rely on is { and }, so I'll just leave this issue here :)

One thing that could be improved over Vim is ignoring whitespace, where a line with only whitespace could be considered empty.

Thank you for your writing nice extension!

I can't input + in insert mode.

If I input +, it turns out to * on each two times input just like
+++++++++++++++

vsCode: Version 0.10.2 (0.10.2) 7cc0c602a2b802b09a3f56b68a1a61ee9e8f0066
OS: Mac OSX Yosemite
Keyboard: US

I am using a block cursor, but in insert mode it goes to a line cursor. Any idea how to fix this? Or is it just impossible in the current release?

Windows用には、オプションIsJisWinKeyboardを用意して、キーの読み替えで対応できそうなことを確認済み。

• VSCode Version: 1.1.0
• OS Version: Windows 10 (Insider Preview Build 14342)

It seems that pressing u will undo multiple editting, if each one is splitted by Esc rather than Enter.

For example, if I i something at one line, then Esc and go to another line, then i something, then pressing u, both the two editting will be undo, rather than the last one.

This behavior is different from GVim 7.4.977 on my computer and often destorys my work if I edit lots of lines without adding a new one.

This problem seems to be talked in #25 and I've checked microsoft/vscode#4313. However, when I use Python: Sort Imports extension to test the issue, the Ctrl-Z works just as expected.

Since amVim has the same problem, I don't know whether the problem with Microsoft has been fixed.

Thanks!

This question is related to support for motion with jkl;,

I'd like to map jj (double j) for Esc and I'm trying this keybindings.json setting, but without any success:

{
    "key": "jj",
    "command": "vim.Esc",
    "when": "editorTextFocus"
}

Is jj be feasible?

I've added the ability to display the current mode in the status bar in PR #11

INSERT Mode:

NORMAL Mode:

NORMAL Mode after 'd' has been pressed once:

Seems undo not work, and when I use G, it didn't work as expected.
Anyway, wish this can work well on VS code, really need this :)

After only a few minutes of usage on Mac OS X the extension completely stopped working. no letter keys will work, though arrows still move the cursor. I would provide logs but I dont know where to find them

When using this with GuidLine installed. GuidLine will nor working.

• gg
• ]}

Example:
"This is text"
with cursor at 'T', execute di"

Expected result:
""

Actual result:
"This is text"

Running VS Code 1.2 on Win7.
vimStyle 0.3.9

Only thing unique about my settings.json is configuring a proxy.

As titled. This is a very common mistake by vim emulator implementors.

Hi - not sure if it's a feature or mistake, but I'm seeing this weird overlay after typing Esc for view mode then i for insert mode, then as I type along the gray overlay extend with my cursor, which makes the code looks really ugly...

There may be some bugs I cannot found. Please report bugs!! Word motion has many function!

aaa bbb ccc
^ dw

except:
bbb ccc

actual:
ccc

Thanks for the plugin.

It looks like the following user prefs are not working when the vimStyle plugin is enabled

"editor.formatOnType" : true,
"editor.autoClosingBrackets": true

when the editor in vim mode ,I input Chinese,but I don't want it,then I press 'shift'.
I expected this operation to avoid typing text,but it failed,it replace the charactors besides the cursor position. And if I user vim or amVim it won't have this problem.

Would it be possible to support the 'J' command, which joins two or more lines?

We added screen line/character movement command in Visual Studio Code in July. The commands is like

cursroMove({to: 'lineStart', inSelectionMode: true});

More details are listed in microsoft/vscode#2771 . Leveraging thse commands, following Vim commands can be implemented real quick

• g0
• g^
• g$
• gm
• gj
• gk

There is no mention of support for .vimrc, _vimrc or a variation in the docs/README.

Scanning through the source code shows nothing related to use of the config files.
Is it considered, planned?

(This is somewhat related to #19 issue.)

Many of Vim users prefer the ergonomic jkl; over the historic hjkl.

As there is no plan to support .vimrc of any kind, please add support for configuration setting to enable switching between those two mappings.

When I move the cursor on the letter e in the normal mode,
all the rest of e are highlighted.

Is it a feature or a bug? If former, can I turn it off in the settings?

https://marketplace.visualstudio.com/

my env:

• vimStyle 0.3.12
• vscode 1.3.1
• system window 10

maybe other multibyte characters has the same problem.

Steps to reproduce:
Delete line using dd and place the line with p and you'll get the expected behavior.

Delete to end of another line using d$ and then attempt to place that text elsewhere with p and you'll see that the contents of the first dd operation is inserted instead of that from the d$ operation.

Example line:
This sentenze has a typo.

This can be reproduced using the following steps:

1. Move your cursor to the word sentenze
2. Type ce.

Actual result:
This ss a typo.

Expected result:
This s has a typo.

Just wanted to say, Thanks for doing this project.

However, one thing which is causing problems for me right now, is that using 'j' and 'k', for navigating up and down a text file doesn't scroll the displayed text, so when I navigate off screen, it still displays where I was already.

Obviously, it would be great if the displayed text would move as well when we press 'j' or 'k'.

probably, judge of line end has a bug.

When holding the movement keys like hjkl(;)w, the cursor will blink between a former position and a newer position, which looks really strange and significantly disturbs editing. What's the problem? What additional information should I provide?
Thanks!

It would be great to have a setting to enable the insert mode by default instead of starting in normal mode.

After installing this plugin and restarting visual studio code I get a warning like
"No handler found for the command: 'vim.j'"
pop up for every key I press inside the editor. Attached is my version information and what I see in the editor with the plugin installed

Not sure if I'm just missing something or if this is a bug.