Made one of these to enter and exit strafe mode in Quake, way back before decent mice were commonly available. It worked fine; I put it away when I got my first Razor Boomslang.
Vim clutch
181–190 of 227 posts
Re: Vim clutch
#182Earlier quoted context omitted.
For what it's worth, I remapped vim's navigation keys from the awkward hjkl to the normal inverted-T arrangement i,j,k,l. Then I remapped the inserts, i & I, to h & H. With that, my natural finger movement on the arrowkeys and on the vim home row match each other. The reason vim's navigation keys (hjkl) today are arranged the way they are, left-means-down and right-means-up instead of up-means-up and down-means-down,…
ijkl sounds good, but it would break my habits for when I play nethack...
Indeed. Remapping inventory would be horrible.
Re: Vim clutch
#183Earlier quoted context omitted.
My very first comment gave some (superficial) explanations. I didn't think that I needed to write a small term paper to voice an opinion. As for down-voting on HN. There's plenty of evidence that it is badly broken. It's funny to watch the Apple fan-boys down-vote on emotion when you even peripherally chafe their idols. The emotion is evident from the fact that substantive posts are down-voted when nothing is materia…
Trollish nonsense. You haven't even really read my comment, or you'd know that the leverage ratio I mentioned, which you're challenging me to justify, was actually about the efficiency of the tools you yourself were touting, not vim. Your "conclusions" are obviously trolling.
Trolling. Really?
This guy is expressing an equally valid argument. And one that I suspect a fair portion of HN readers agree with.
Personally, I thought it was April 1st when I saw a foot pedal for a text editor!?
Accusing him of trolling is really lowest-common-denominator fanboi bullshit. He makes valid arguments, agree to disagree and move on.
Re: Vim clutch
#184Earlier quoted context omitted.
You have to learn h,j,k,l are not just navigational keys but also can be combined with multipliers like 20h(Moves 20 positions to the left). You know, I've understood this for a while, but to this day I still don't use it. I can't count characters that fast! If you're going to lean forward and count out chars, you might as well count them out with presses of 'h'.
For what it's worth, I remapped vim's navigation keys from the awkward hjkl to the normal inverted-T arrangement i,j,k,l. Then I remapped the inserts, i & I, to h & H. With that, my natural finger movement on the arrowkeys and on the vim home row match each other. The reason vim's navigation keys (hjkl) today are arranged the way they are, left-means-down and right-means-up instead of up-means-up and down-means-down,…
People always treat hjkl as the single biggest roadblock to vi(m) adoption, and I don't get it. Two points:
* First and foremost: If you rely on hjkl, you are doing it wrong anyway. You should be using f, w, ), :n (for integer n), ^d, ^f, etc. My biggest hjkl use case is using j to idly scroll through a file (or less/more/man page), in which case it's conveniently under my index finger and I love it. I also use l for off-by-one errors.
* Secondly...especially now that it's ingrained, all of the other keys "make sense" (sort of), and there's no excellent alternative. With your setup, "Why is h insert? Wouldn't i make more sense? Gosh, vim is hard to use." Etc. etc.
Re: Vim clutch
#185I don't know how this would work out ergonomically. My dad is a cab driver and he often complains that pressing the clutch with his foot often giving him RSI kind of pain. But however I think this is purely subjective. From an experiment perspective, this is really cool! And this generally qualifies into what could one call a 'real hack'. This has a air of freshness to it. Now the real power of vim is in getting into…
You have to learn h,j,k,l are not just navigational keys but also can be combined with multipliers like 20h(Moves 20 positions to the left). You know, I've understood this for a while, but to this day I still don't use it. I can't count characters that fast! If you're going to lean forward and count out chars, you might as well count them out with presses of 'h'.
Just use f and ; judiciously.
Re: Vim clutch
#186Earlier quoted context omitted.
> why is it that you seem so intent on discrediting the experiences of others? I think you are reading far too much into what I've commented. Nobody is doing that at all.
People are telling you that they find vi style editing to be beneficial or valuable for efficiency reasons, and you seem to me to be dismissing this. That is what I would call discrediting the experiencing of others.
I think you're both arguing different things:
jlgreco: vi/vim is an efficient text editor when you learn it! And even more efficient with a foot pedal! Don't discredit our time spent learning vi/vim when it is in fact an efficient text editor!
robomartin: vi/vim may be an efficient text editor, but in the grand scheme of a large(non-trivial) project, small improvements to text editing efficiency are irrelevant. Particularly at the sake or cost of learning and mastering vi/vim. There are easier-to-learn and more-intuitive text editors available now.
Both valid points.
Re: Vim clutch
#187Earlier quoted context omitted.
Here's opinion from the horse's mouth: Back in 1999, the mag asked Joy what inspired him to write vi: What happened is that Ken Thompson came to Berkeley and brought this broken Pascal system, and we got this summer job to fix it. While we were fixing it, we got frustrated with the editor we were using which was named ed. ed is certainly frustrating. We got this code from a guy named George Coulouris at University Co…
Editing efficiency, which is what everyone else here is talking about, is (I suspect), completely unrelated to business efficiency (which seems to be what you are primarily talking about). Your Bill Joy quote is talking about editing efficiency. I do not suggest that editing efficiency has a measurable impact on business efficiency, and I do not see anyone here suggesting that it does. You seem to be under the impres…
Unless your programming is a hobby, then it IS business. It sure is to the guy paying the bills.
Imagine a conversation like this:
PROGRAMER: "Hey, boss, on Monday we want to switch to
vi/m because everyone says it is more efficient".
MGR: "Do you have any data to support that? Will the
project get done on-time, on-budget, faster, better
and with less bugs?"
PROGRAMMER: "Well, I can't guarantee any of that and
can't offer quantifiable data, but programmers who know
it swear by it and talk about how much more efficient
it is."
MGR: "It only makes sense to me if you can prove and
guarantee that switching from our current text editor
to vi/m will result in true and measurable productivity
and quality gains. Otherwise there's nothing in what
you are saying that justifies changing over."
Boy, does one have to have a thick skin to voice contrasting opinion on HN sometimes.
Re: Vim clutch
#188Very nice. But why put something like this on GitHub?!!
I hope that it does not become a trend to create repositories for every blog post. Github is not a personal blog, and I don't think it should be used as such.
Re: Vim clutch
#189I did this a few months ago: imap kj I have never had to type a word with the letter combination 'kj' in it. Works great.
That's going to suck when you get lockjaw playing blackjack in Reykjavik. But other than that, you seem pretty safe.
There goes my plan for my Icelandic-themed casino site.
Re: Vim clutch
#190Very nice. But why put something like this on GitHub?!!
I hope that it does not become a trend to create repositories for every blog post. Github is not a personal blog, and I don't think it should be used as such.