daveosborne / brackets-vimderbar Goto Github PK

Many commands present choices for code completion when they should not. For instance 'dd' deletes a line, and then suggests some code. This shouldn't happen since it is in command mode.

Code completion suggestions also occur in insert mode when they shouldn't - for instance, when the 'o' command is given to start a new line, code is immediately suggested before anything is typed. Code suggestions also happen when doing a simple 'delete' or 'backspace'.

The 'G' keybind only works if you're holding shift, rather than if caps-lock is on.

I try ":set clipboard=unnamed", but it doesn't work. Which the .vimrc file is using?

The README suggests that yy and dd (or possibly y and d in Visual Mode) aren't working, but they're working fine for me in Sprint 26.

Great extension, BTW, thanks!

In Vim, as well as many of the other vim keybinding plugins I've used, typing S in normal mode deletes everything in the line except indenting spaces/tabs and puts you into insert mode. In your plugin, it simply deletes the whole line (INCLUDING the indenting spaces) and puts you into insert mode. It would be nice if this behaved as expected, especially because vimderbar also disables soft tabs.

Looking into it, seems that the vim keymap is broken and/or mode switching is broken.

Hello,

if Vimderbar is installed and enabled, Brackets ignores indentation preferences. Whenever the tab-key is pressed, a tab character will be inserted. This results in having mixed spaces and tabs.

Brackets: Sprint 40 development build 0.40.0-0 (master 4d9502f14)
Vimderbar: 0.4.10

cannot move with enter key on html files, i tested on css files and work but not on html, anyway to fix it?
thanks

In vim, r is used to replace a single char with another, . is used to repeat last command. However, this two does not work together here.

For example, I have

#abc
#abc
#abc

If I use r to replace first # with ., it changes to

.abc
#abc
#abc

However, when I move to second line, use . command to repeat last command, I get

.abc
..abc
#abc

What I expect is

.abc
.abc
#abc

If I use . to repeat command in the third line, I get

.abc
..abc
....abc

When vimderbar is enabled (i.e. in the 'user' extensions folder) I noticed a very strange behavior :

Steps to reproduce :

1. Open brackets (brackets loads last known state of a project with at least 2 "working files".
2. Edit 1 file (let's call it File A)
3. Click on another "working file" (File B)
4. Edit it normally. When trying to delete a character using backspace or del

-> It edits File A at last known cursor position (deleting characters)...

Nota Bene: I'm on linux mint debian x64, running brackets sprint 41 (observed this problem since sprint 39 at least).

Hi, I'm use your extension but need some help with configuring it. For example if your current language not English (russian for example) codemirror can't recognition any commands (for example hjkl navigation) in normal mode. In vim we can map bindings like this:

map й q
map ц w
map у e
map к r
map е t
map н y

or setup vim like this:

set keymap=russian-jcukenwin
set iminsert=0
set imsearch=0

but I'm newbie with codemirror and your vimderbar, please help with setup.

I know you only support basic commands, so that's why I'm adding this as an issue :) ctrl+d should scroll down.

The shortcut for toggling comments (Ctrl+/) when used in --Visual-- mode and multiple lines are selected properly insert the close comment but the syntax highlighting doesn't properly update. Only the line that has <!-- and the line under it are highlighted as comment lines but the rest stay the same. If then the u (undo and Ctrl-Y for redo) are pressed the syntax is okay. Similarly the Ctrl+Shift+/ breaks the syntax highlighting as well.

Edit:
Okay it only seems to happen if one selects the last line of the multiline selection (which contains the closing tag), if one instead selected the empty line below the closing tag it properly applies the comment highlighting.

It would be nice if brackets would remember that vimderbar was enabled after closing and reopening

my os is win8.1 and 64bit
brackets Release 1.2 build 1.2.0-15689 (master 97c3a4cde)

I install vimderbar ,

I want to back view mode，i press esc ，but it's invalid

sorry ,my English is so bad，I hope you to understand what i said

Since the update to brackets 1.2 I can no longer hold down ex. "j" to move the cursor down continuously, it simply stops as if I pressed "j" once.

I noticed that the x-command behaves differently from Vim in my terminal.
For example, considered the following line of text

Lorem ipsum dolor sit amet, consectetur adipiscing <cursor>elit

Note that the cursor is at <cursor> :)
Now, when I press (and hold it down) x what will happen is that it will delete the character following the cursor (in this case elit). If these are deleted, it will continue with the character preceding the cursor, but this is not what happens with vimderbar. Vimderbar only deletes character after the cursor.

I don't know is this is intended, but I would really like to see that the x command also delete character preceding the cursor as well. Is this possible ?

Hello,

What is the correct way to get toggleVisualMode, blockwise:true to work? I can't seem to get the syntax in the Brackets.json file to make it happen. I'd be fine using Alt-v, so the C-v paste wouldn't be overridden, or some other keymapping, even, but I can't seem to get Vimderbar to recognize the block visual mode part.

Thanks,

Mark

Haven't extensively tested this, but with vimderbar disabled I normally see this:

And once I enable it and get inside a HTML tag, the cursor goes missing like this:

I've removed all other extensions and using sprint 34 (latest).

Hi,

First of all, let me say I'm glad to see vim bindings coming to brackets :)

I find very distracting (and actually annoying) the blinking cursor. Could there be an option to have it steady?

Hi! Brackets now has a built-in Extension Manager that lets users browse and install extensions from a central registry. It would be great if you could upload your extension to the registry--over half of the extensions on the old "Brackets Extensions" wiki page have moved over already, and eventually we'd like to get rid of that page altogether.

Here's more info on how to upload your extension to the registry: https://github.com/adobe/brackets/wiki/Extension-Registry-Help. It's pretty simple: you just have to create a package.json file if you don't already have one, make a zip file, and then drag and drop it into the registry web app.

Thanks!

When performing commands with iw (inner word) , last letter of the word is not treated :
abcde --> ciw (cursor on any letter) then p --> abcd
abcde --> diw (cursor on any letter) --> e

After a few tries, the problem is not met when using same commands with iW.

The s key works perfectly when substituting a single character, but if you select a range and then press s the cursor moves 1 character to the right.

Description:
PageUp/PageDown does not behave as expected in Visual select mode.

Steps to reproduce:

1. Open any file.
2. Start a Visual selection with v or Shift-V.
3. Press PageUp/PageDown

Observed Behaviour:
PageUp moves to the start of the selected area, and PageDown moves to the end of the selected area.

Expected Behaviour:
PageUp/PageDown should move the cursor up/down a page, and change the selection to be from the original selection point to the new cursor position.

Platforms:
I am able to reproduce this on a base install of brackets/vimderbar under Ubuntu 13.10 and Windows 7.

When hitting :#, such as :1, the editor moves to the first line as expected. However, the editor seems to have lost focus requiring me to mouse click in to resume editing. It's a little thing, but just wanted to let you know.

Cheers and good work!

I'd like to implement some of the keybindings in my vimrc file - any documentation you can point me towards?

On a fresh install of brackets and vimderbar on OSX, keystrokes do not seem to repeat if you hold down the key. For example, holding down j/k to move the cursor up/down a document causes the cursor to move only once. Similarly, holding down the 'a' key in insert mode only causes one 'a' to be inserted.

In command mode, move cursor to first letter of a word. Press "ve". This should highlight all characters in the word, but it stops before the last letter.

e.g. Intended to highlight the word "status". With cursor at the first s, type ve, only "statu" gets highlighted. de and ce both work as expected.

Also, the "vi" command doesn't seem to work well, if at all. e.g. vi( and viw both apparently do nothing.

Thanks for this awesome plugin!

When I press } I go to the next paragraph, but when I press { it actually types a { instead of going to the previous paragraph.

I'm running brackets-git under linux.

I've encountered strange behaviour of :w being slower and slower each time I save my document. After a couple of minutes it's hardly usable.

When I use ctrl+s it works fine as usual even if :w takes like a second. Will try to deliver more info if you wouldn't be able to reproduce it.

I am new in vim. When I am using sublime I can easily change the vim "exit insert mode" keybinding. But I can't in Adobe Bracket. I would like to use jj shortcut instead of
👍 Thanks man for making this awesome plugin. It saves me. I love brackets but lack of vim plugin I didn't use brackets. Now I am using brackets with assist of your plugin

Sorry to bug you with this, but I'm trying to enable the Vimderbar extension in the Intel XDK version of Brackets, but it doesn't show up in the Available tab of the Extension Manager. Can you tell me how to install it manually or provide some workaround?

Thanks in advance,

Mark

Hi guys,

I would like to add a keybinding toggle vimderbar state (enabled/disabled) using the User Key Map or the Brackets key remapper extension.

...but I can't find the valid commandID (if there is one). I tried view.enableVimderbarand vimderbar.enable.

Is this actually possible?

What is the correct way to map Ctrl + [ to exit insert mode?
I tried "vimderbar.mappings": [{"keys": "<C-[>", "toKeys": "<Esc>", "mode": "insert"}]
but it did not work

Here's the definition of the macro:

qa
^
cf[
i $headers->set(
esc
f]
cf=
,
esc
$
i )
esc
j
q

Here's the code I'm running it on:

  $res['Content-Disposition'] = 'attachment; filename="'. $filename .'"';
  $res['Content-Length'] = '' . filesize($file);
  $res['Content-Range'] = '';
  $res->setBody(file_get_contents($file));

And here's what happens when I go to run the macro:

This seems really unintuitive to me - I don't believe I did anything wrong, macro-definition-wise. Though certainly correct me if I did - I am, at best, at amateur vim user (vimmer? vimolyte?).

EDIT:

This is on OS X 10.9 (not Yosemite), using Brackets Release 1.2 build 1.2.0-15697 (release 8f82e2a97) -- the most up-to-date version of Brackets, so far as I am aware -- and the most recent version of vimderbar as well.

First off, thanks for working on this--I don't know why I hadn't seen it on the Brackets extension listing page before (a bunch of people have been bugging us for Vim support :))

One issue I ran into when I was investigating Vim support myself earlier was what to do about inline editors (also known as Quick Edit). Currently, Esc is bound to closing the current inline editor (or all inline editors if focus is in the main editor). That makes it hard to use vim mode inside inline editors, since trying to get out of insert mode closes the editor as well.

I'm not sure what the best solution is from the user's point of view. One solution would be to have the vim extension unbind Esc from closing inline editors and assign some other key to it.

Another solution would be to make it so that if you're in an inline editor in (say) insert mode, the first Esc would just quit out of insert mode, and the second one would collapse the inline editor.

Since I'm not a vim guy (I can find my way around it but don't use it regularly), I'm not sure which of those behaviors would be more desirable. I expect the first one might be--my guess is that vim users probably are in the habit of hitting the Esc key even if they're not in insert mode (just to make sure they're out of it), and so having it be overloaded in inline editors might just be frustrating.

(It also turns out that neither of them is easy to implement with the current Brackets codebase...but if we could get an idea of which one is better, we could figure out some solution.)

Not sure if this is still maintained at all, but the Esc key does not work now. I am on macOS Catalina 10.15.2 with build 1.14.1-17752.

With VI enabled the autocomplete functionality is triggered when you hit (in command mode) o or dd. I think that the correct behaviour is to only do this when you start typing (this seems to be the default brackets behaviour). When you do A for example, the autocomplete only shows when you start typing, which is good (but inconsistent with o and dd)! As it works now, it is especially annoying when, for example, you hit dd and want to navigate with the arrow keys, because you then navigate inside the autocomplete dropdown.

Below is a screenshot of what happens when you hit o
.

In Normal mode, when I want to advance to the next character '/', I press 'f' and '/'. It does bring the cursor to the next '/', but the search bar is also opened.

In Vim, when you search, it show highlight. But after you open another file search another text and go back before file. the highlight always here, can not be remove.

Hi,

Is there a way to set up buffer switching using (http://superuser.com/a/486535)? I'm fairly used to this in vim and I keep closing files. I'm new to Brackets so I'm not sure if this would preferably be configure in user keybindings. Also thanks for the plugin! Wouldn't be using Brackets without it.

James

Are you planning on adding support for the "qa" command to record your actions. As of now it does nothing and just puts me in insert mode after the cursor.

Thanks

I wonder if you've noticed that the extension somehow captures the Tab key and inserts \t even when the brackets config is set to insert spaces. I ask this because after un-installing vimderbar the behaviour went back to how I expected it to work.

I looked through the vimdebar code but didn't find any mention of tab key capturing, maybe you have some insights.

Having wasted some time on this problem myself - finding your working extension was a welcome relief from the clown punching good time trying to untangle javascript. Kudos sir - you have a fan on the internet.

  > this guy! <

Hello,

not sure if this is problem with CodeMirror or what, since the Vim keybindings demo on CodeMirror web site doesn't have this problem.
But, the problem is, when I use b and w keys to jump over whole words, it stops at the ä characters in the word and does not jump over it.
For example, if I have word täällä and I place the cursor in front of that word, I need to type w multiple times to get over that word.

Just installed the latest version (0.3.2), things are looking good :-)

One issue: I tried to use this ex command:

:%s/black/darkgray/g

It replaced the word on the current line but then stopped, and in the status bar this error:

TypeError: Cannot read property 'line' of undefined

cit support.

In Vim, when you search, the highlighted result is not visually selected - it's just highlighted. Highlighting and visually selecting text are two different things.

I want to do
inoremap jk <Esc>

I followed the docs about user custom key remappings and inserted the following in brackets.json:

"vimderbar.mappings": [
        {"keys": "jk", "toKeys": "Esc",  "mode": "insert"}
    ]

When I press jk in insert mode, jk is deleted but vimderbar still stays in insert mode. Do I miss something here or is this a bug?