t9md / atom-vim-mode-plus-ex-mode

Experiment to implement ex-mode for vim-mode-plus
https://atom.io/packages/vim-mode-plus-ex-mode
MIT License
30 stars 11 forks source link

: not working on Atom version 1.7.4 Mac OS 10.11.4 #9

Closed yuzhoul1991 closed 7 years ago

yuzhoul1991 commented 8 years ago

It seems typing : does not do anything now on the Atom and Mac OS version mentioned in the title. Windows seems to be okay. I did disable the official vim mode and ex mode but did not uninstall them as this version of Atom has a bug of not being able to uninstall packages.

mahmoudhossam commented 8 years ago

I have the same problem on Atom 1.9.6, Arch Linux x64.

t9md commented 8 years ago

Whats your keymap setting? Does keymap resolver report correctly invoke vmp-ex-mode's command?

mahmoudhossam commented 8 years ago

I put the code in the readme in my keymap.cson but I can't find anything in my keybindings when I search for ex-mode.

mahmoudhossam commented 8 years ago

After restarting atom, the shortcut now works.

fohrums commented 8 years ago

Confirmed. having an ex-mode to work alongside a Vim package just simply doesn't work with Atom_1.9.9 + Windows 10 also.

Atom_1.9.9
win10_Home_x64

VIM-PACKAGES INSTALLED

PROBLEM

WHY EVEN EX-MODE?

NOTE

t9md commented 8 years ago

@fohrums This issue is solved already. your issue is completely new one? not sure.

Did you set keymap in your keymap.cson? How about excuting Vim Mode Plus Ex Mode: Open from command palette. If you set keymap described in README.md, what keybindig-resolver says against your : keystroke.

For windows issue for ctrl-w to close pane-item, see this links.

fohrums commented 8 years ago

@t9md,

Did you set keymap in your keymap.cson (just like in README.md)?

Thanks this did solve the issue and it's best to note that it doesn't act like vim's own : traditionally;... instead, what you get is Atom's flavor through the use of it's own searchbar as the ex-mode. I was confused for a bit and didn't realize this new search bar WAS indeed the ex-mode (hence, the as-mentioned bolean config parameter).

I would suggest letting users know how to navigate to keymap.cson to add these custom key-bindings that are specific to your vim-mode-plus-ex-mode package. That is, because just simply stating the following doesn't let me know what I need to do exactly:

@vim-mode-plus-ex-mode_README.md There is no default keymap.


So, i've re-created that step for you. All you need to do know is update your README.md to suggest this...

PRE-REQUISITE (vim-mode-plus-ex-mode)

'atom-text-editor.vim-mode-plus.normal-mode':
  ':': 'vim-mode-plus-ex-mode:open'
  '!': 'vim-mode-plus-ex-mode:toggle-setting'

ENJOY!!


For windows issue for ctrl-w (as it's currently defined as a prefix-key) to close pane-item, see how to solve this issue here..

Man,....you don't change what is common & you don't build over existing structures.....but these decisions made by Atom makes me wonder, pffft. I would be a happy camper with npp but it's vim plugin visimulator has by default not enabled the keymapping CTRL-[ to escape current modes and closing npp will remove the save setting to have it enabled in the first place. Just that lil' effort missing made me switch to Atom COMPLETELY at a hunned!

bronson commented 7 years ago

Sounds like it's working for everyone (including me). Seems like this can be closed...?

t9md commented 7 years ago

Thanks @bronson , will close.