4 ms·

The kevincolyar account does nothing but spam HN with links to his application. I am sick of seeing him post spam each time a VIM article hits the homepage.

by steve19 16y ago

stevelosh 16y ago
I'm the author and submitter of the post and for what it's worth I don't mind his comment at all. It's relevant because OS X Vim users would probably like to use Vim movement everywhere. I know I would. It's certainly more relevant than the "use emacs lol" comments that inevitably show up.
- mikecaron 16y ago
  Yeah, the whole vim/emacs war is so 1995.
kevincolyar 16y ago
I'm just trying to get what I think is a useful application into the hands of the people who would find it useful. If you find that irritating, just keep scrolling by.
- blasdel 16y ago
  Try contributing to discussions instead of copy-pasting the same promotional tagline. You could also make some effort to actually understand vi — your app doesn't take you out of insert mode! Using hjkl and ypu does not somehow make anything vi-like when there's no command mode, no compositionality, and a hotkey that breaks everything else. Seriously, chording‽ If you're going to chord for movement just use the built-in emacs bindings! Instead of ^hjkl it's ^bnpf, if you really want to do something as inane as use modified letters as arrow keys. Why did you write your cargo-cult app at all? There's at least a half-dozen InputManagers that implement true vi command modes already, and while nobody actually uses them, at least their authors appear to have actually used a vi editor before!
  - kevincolyar 16y ago
    I'm sorry you don't find ViKing useful. It's not meant to replace vi, it's simply meant to be a tool that vi users might find useful. I know many who do. I assure you I do understand vi. I use it everyday. I've explored the idea of making ViKing modal but based on user feedback have decided not to go that route. I am aware of the InputManagers you mentioned but I believe I'm solving a different problem. Thank you for your feedback, though. I do appreciate it. God bless.

The kevincolyar account does nothing but spam HN with links to his application. I am sick of seeing him post spam each time a VIM article hits the homepage.

by steve19 16y ago

The kevincolyar account does nothing but spam HN with links to his application. I am sick of seeing him post spam each time a VIM article hits the homepage.

stevelosh 16y ago

I'm the author and submitter of the post and for what it's worth I don't mind his comment at all. It's relevant because OS X Vim users would probably like to use Vim movement everywhere. I know I would. It's certainly more relevant than the "use emacs lol" comments that inevitably show up.

mikecaron 16y ago
Yeah, the whole vim/emacs war is so 1995.

kevincolyar 16y ago

I'm just trying to get what I think is a useful application into the hands of the people who would find it useful. If you find that irritating, just keep scrolling by.

blasdel 16y ago
Try contributing to discussions instead of copy-pasting the same promotional tagline. You could also make some effort to actually understand vi — your app doesn't take you out of insert mode! Using hjkl and ypu does not somehow make anything vi-like when there's no command mode, no compositionality, and a hotkey that breaks everything else. Seriously, chording‽ If you're going to chord for movement just use the built-in emacs bindings! Instead of ^hjkl it's ^bnpf, if you really want to do something as inane as use modified letters as arrow keys. Why did you write your cargo-cult app at all? There's at least a half-dozen InputManagers that implement true vi command modes already, and while nobody actually uses them, at least their authors appear to have actually used a vi editor before!
- kevincolyar 16y ago
  I'm sorry you don't find ViKing useful. It's not meant to replace vi, it's simply meant to be a tool that vi users might find useful. I know many who do. I assure you I do understand vi. I use it everyday. I've explored the idea of making ViKing modal but based on user feedback have decided not to go that route. I am aware of the InputManagers you mentioned but I believe I'm solving a different problem. Thank you for your feedback, though. I do appreciate it. God bless.