5 ms·

Wow, it's a full vim. I was expecting to find things it couldn't do, but I ran out of things to try. Great work. It did take a little longer than vim to load

by Tyr42 12y ago

Wow, it's a full vim. I was expecting to find things it couldn't do, but I ran out of things to try. Great work. It did take a little longer than vim to load, but I guess that's expected.

jonawesomegreen 12y ago
This was the first thing I tried. Lets see if I can find an unimplemented command. I likewise came up empty handed. Very cool stuff!
- chr1 12y ago
  Well it _is_ the real vim, built with --with-features=small (see https://github.com/coolwanglu/vim.js#vim-features https://github.com/coolwanglu/vim.js#vim-features) so folding for instance doesn't work
- deleted 12y ago
  [deleted]
markus2012 12y ago
It did not work well in Chrome: 36.0.1985.49 beta C-f, C-b didn't even work. I then gave it a shot in Firefox nightly and it seemed to work really well. This brings me joy. I don't like to edit forms/documents on the web; it's a constant struggle against my muscle memory. Vim.js could be the start of something that could change that. Well done!
- gibbonsd1 12y ago
  This doesn't work for me either. However, I am using the Vimium plugin for Chrome which may also cause issues.
  - rifung 12y ago
    Did you try going into insert mode in vimium before trying it?
- Sephr 12y ago
  Chrome 36 beta came out half a year ago. It's unreasonable to expect web developers to support very old versions of a browser that silently auto-updates. Most popular frameworks and libraries, such as jQuery (see https://jquery.com/browser-support/ https://jquery.com/browser-support/), only officially support the latest stable Chrome and one version prior.
  - deathanatos 12y ago
    (Edit: strike point about Chrome release date; had the release-release date, parent probably means when beta started.) I'll also note that in the past, I've purposefully not upgraded due to serious bugs in the present version of Chrome. (There was a great one a while ago where entire websites — notably Wikipedia — were rendering in the wrong font, for example.) > a browser that silently auto-updates While I'll grant that this is true for the majority of users: 1. It requires a user to restart their browser. For me, this usually means the next weekend or Chrome/OS X crash, since during the week I'm usually busy with things other than restarting the browser… 2. Not all OS's auto-update, though this is a very small minority.
  - markus2012 12y ago
    It's unreasonable and unfair for you to assume I have any expectation for Vim.js to work with the version of Chrome I listed. I was merely providing feedback / datapoint.
  - e12e 12y ago
    Right. So it eas pretty new in July, then? https://github.com/coolwanglu/vim.js/commits/master https://github.com/coolwanglu/vim.js/commits/master
jballanc 12y ago
Visual Block input doesn't work (at least not in the newest Safari).
stevebmark 12y ago
It's missing some important Vimities: q/ q: :normal ctrl-n in insert mode (or any completion like ctrl-x ctrl-l) of course plenty of command line options like virtualedit: Though it does implement the expression register ( i CTRL-R = ), the regex class \x (among Vim's other rando regex classes), and :set synmaxcol which is pretty nitty gritty.
- darklajid 12y ago
  I'm a bit ashamed to ask, but .. as someone that is using vim quite a bit (but certainly no expert), I didn't recognize any of those. Can you elaborate and explain what you're missing and what for?
  - stevebmark 12y ago
    If you're using Vim and not using q: q/ :normal ( and hopefully :t, :m etc with relativenumber ) you're missing a lot of Vim's power, and would be better off in an IDE. The speed benefits from Vim are from knowing a large amount of the editor's features. Practical Vim the book is a good place to start. You should be spending as much time learning Vim as using Vim for about the first two years of your Vim usage.
    - darklajid 12y ago
      No offense, but - you haven't answered my question. Like, at all. - I don't quite like the 'would be better off in an IDE' part. That said, at this point I'll better see what I can find about these oh-so-essential features and I might even add them to my routine/workflow (so far, I still don't know why though...). Edit: As expected, the help page doesn't explain why I should care about those. q: and q/ are nothing I ever missed, :normal is weird and I cannot imagine what it is used for. Basically my whole reason to jump on this thread "Okay, now I don't know these. Why are they useful?" is absolutely still relevant. Reading the documentation isn't enough. I .. won't buy a book at this point.
      - stevebmark 12y ago

by Tyr42 12y ago

Wow, it's a full vim. I was expecting to find things it couldn't do, but I ran out of things to try. Great work. It did take a little longer than vim to load, but I guess that's expected.

jonawesomegreen 12y ago

This was the first thing I tried. Lets see if I can find an unimplemented command. I likewise came up empty handed. Very cool stuff!

chr1 12y ago
Well it _is_ the real vim, built with --with-features=small (see https://github.com/coolwanglu/vim.js#vim-features https://github.com/coolwanglu/vim.js#vim-features) so folding for instance doesn't work
deleted 12y ago
[deleted]

markus2012 12y ago

It did not work well in Chrome: 36.0.1985.49 beta C-f, C-b didn't even work. I then gave it a shot in Firefox nightly and it seemed to work really well. This brings me joy. I don't like to edit forms/documents on the web; it's a constant struggle against my muscle memory. Vim.js could be the start of something that could change that. Well done!

gibbonsd1 12y ago
This doesn't work for me either. However, I am using the Vimium plugin for Chrome which may also cause issues.
- rifung 12y ago
  Did you try going into insert mode in vimium before trying it?
Sephr 12y ago
Chrome 36 beta came out half a year ago. It's unreasonable to expect web developers to support very old versions of a browser that silently auto-updates. Most popular frameworks and libraries, such as jQuery (see https://jquery.com/browser-support/ https://jquery.com/browser-support/), only officially support the latest stable Chrome and one version prior.
- deathanatos 12y ago
  (Edit: strike point about Chrome release date; had the release-release date, parent probably means when beta started.) I'll also note that in the past, I've purposefully not upgraded due to serious bugs in the present version of Chrome. (There was a great one a while ago where entire websites — notably Wikipedia — were rendering in the wrong font, for example.) > a browser that silently auto-updates While I'll grant that this is true for the majority of users: 1. It requires a user to restart their browser. For me, this usually means the next weekend or Chrome/OS X crash, since during the week I'm usually busy with things other than restarting the browser… 2. Not all OS's auto-update, though this is a very small minority.
- markus2012 12y ago
  It's unreasonable and unfair for you to assume I have any expectation for Vim.js to work with the version of Chrome I listed. I was merely providing feedback / datapoint.
- e12e 12y ago
  Right. So it eas pretty new in July, then? https://github.com/coolwanglu/vim.js/commits/master https://github.com/coolwanglu/vim.js/commits/master

jballanc 12y ago

Visual Block input doesn't work (at least not in the newest Safari).

stevebmark 12y ago

It's missing some important Vimities: q/ q: :normal ctrl-n in insert mode (or any completion like ctrl-x ctrl-l) of course plenty of command line options like virtualedit: Though it does implement the expression register ( i CTRL-R = ), the regex class \x (among Vim's other rando regex classes), and :set synmaxcol which is pretty nitty gritty.

darklajid 12y ago
I'm a bit ashamed to ask, but .. as someone that is using vim quite a bit (but certainly no expert), I didn't recognize any of those. Can you elaborate and explain what you're missing and what for?
- stevebmark 12y ago
  If you're using Vim and not using q: q/ :normal ( and hopefully :t, :m etc with relativenumber ) you're missing a lot of Vim's power, and would be better off in an IDE. The speed benefits from Vim are from knowing a large amount of the editor's features. Practical Vim the book is a good place to start. You should be spending as much time learning Vim as using Vim for about the first two years of your Vim usage.
  - darklajid 12y ago
    No offense, but - you haven't answered my question. Like, at all. - I don't quite like the 'would be better off in an IDE' part. That said, at this point I'll better see what I can find about these oh-so-essential features and I might even add them to my routine/workflow (so far, I still don't know why though...). Edit: As expected, the help page doesn't explain why I should care about those. q: and q/ are nothing I ever missed, :normal is weird and I cannot imagine what it is used for. Basically my whole reason to jump on this thread "Okay, now I don't know these. Why are they useful?" is absolutely still relevant. Reading the documentation isn't enough. I .. won't buy a book at this point.
    - stevebmark 12y ago