I cannot wait for the port of NativeClient
Vim ported to iOS
71–80 of 133 posts
Re: Vim ported to iOS
#72Vim is for coding. How does this work out on the iPad? Does one edit remote files locally, and compile/run remotely? (the benefit is the editing feels instant - no keystroke latency.) Or has Apple let up on the "no coding for you!" iPad/iPhone terms? (I thought they would eventually, once their dev environment is firmly established - and they'll have to, if/when they adopt iOS on their {lap,/desk}tops - but maybe tod…
> Vim is for coding.
Yes, and a lot more. I use Vim for all my text editing.
I used vim to write my latest blog post. It would have been (and will be) awesome to do that on my iPad instead.
Re: Vim ported to iOS
#73Re: Vim ported to iOS
#74Earlier quoted context omitted.
That's great for browsing but I can't picture coding in an editor where I need to stop and look for common command keys. At the moment vim is efficient because [esc]10dd or something but it's just not viable without a keyboard. For reviewing code or making quick edits however this could be incredible. I wonder if it supports plugins.
nnoremap jk
I actually prefer kj myself, as it's a little faster to go from outside to inside fingers.
Re: Vim ported to iOS
#75Yet another emacs/vim article, and I always look for an excuse to get excited but never can. It seems that the speed at which I think/code is much slower than the speed at which I type. So I can't imagine that I would benefit from skills in emacs/vim-fu. Is this preconception valid, or can anyone debunk?
This is a circular argument (or some sort of thing like that), but if you ever find yourself at a *nix command line prompt and need to edit a file, you can be certain that vim will be available. Basic familiarity with it can be helpful. Personally, I used to write a ton of perl inside Vim as a student, but these days I'm in VS all the time, and only use Vim like I would use Notepad - when I want to do quick edits in…
> but if you ever find yourself at a nix command line prompt and need to edit a file, you can be certain that vim will be available. Basic familiarity with it can be helpful.
True, but I've been getting by for the last 20 years with little more than 'i', 'x' and ':wq' (or ':q!') for changing system settings. The point of mastering vim as an efficient code editor is far beyond what you need to get your nix settings sorted.
Re: Vim ported to iOS
#76Yet another emacs/vim article, and I always look for an excuse to get excited but never can. It seems that the speed at which I think/code is much slower than the speed at which I type. So I can't imagine that I would benefit from skills in emacs/vim-fu. Is this preconception valid, or can anyone debunk?
This is a circular argument (or some sort of thing like that), but if you ever find yourself at a *nix command line prompt and need to edit a file, you can be certain that vim will be available. Basic familiarity with it can be helpful. Personally, I used to write a ton of perl inside Vim as a student, but these days I'm in VS all the time, and only use Vim like I would use Notepad - when I want to do quick edits in…
[deleted]
Re: Vim ported to iOS
#77What's the biggest advantage over SSHing to your server? Is the interface optimized? I mean, you're almost never offline these days, so local storage can't be it, right? I suggest mapping 'jj' to ESC rather than '\'
Small tip - I use "jk" instead of "jj" for ESC.
I always thought the difference was personal preference, but there is actually 1 good reason to use "jk". If you get used to pressing "jk" all the time, you'll probably end up using it in Normal mode as well as insert mode. "jj" will move up 2 rows in Normal mode, while "jk" doesn't do anything. Therefore you can use "jk" as a reflex every time you get to the keyboard, and it won't screw you up.
Re: Vim ported to iOS
#78I've been wanting vim support on the iPhone for a while.
I actually think it's a big thing that would work well on the iPhone. The whole point of vim is that, with only a few keys, you can navigate anywhere you want extremely quickly. Most of the limitations of the iPhone are things like "can't see many keys at once", and "hard to go to specific lines by dragging your finger around the screen", etc. Vim on the iPhone can fix all that.
Haven't seen this app though, off to play with it. Hope they did a good job :)
Re: Vim ported to iOS
#79Pretty epic. Nothing more.
I think I'm crying.
Re: Vim ported to iOS
#80Earlier quoted context omitted.
I think they're called "guidelines" for a reason, and nowhere in them is the word "prohibited" used.
Except that in the vast majority of cases, not following them really hurts your chances of getting into the App Store. Try to find a few other apps on the App Store that you can exit from within the app, to get a sense of just how much of a "guideline" this really is.
I can see two likely scenarios why this got passed:
1. The reviewer has never used vim. As someone unfamiliar with vim, it never occurred to them to type :q, and thus they never saw that behavior.
2. The reviewer has used vim before, and knows how it works. With that familiarity, the reviewer understood that :q quitting the app was the behavior that users would expect.