Vim Croquet • Hacker News Board

Re: Vim Croquet

#21

Post by nathan_long » Tue, Jan 28, 2014, 9:01 PM UTC

Awesome! I'd love to see something like this as a standalone project. "Vim Critic" or "Vim Coach" - something to say "these are the inefficient things you personally do."

Probably some low-hanging fruit would be "any keystroke in Normal mode that's repeated." Eg, if I'm doing 'jjjj' to move down or even 'wwww' to hop from word to word, I could be searching or using a movement combo like '4j'.

Re: Vim Croquet

#22

Post by mercurial » Tue, Jan 28, 2014, 9:48 PM UTC

ajanuary wrote: post #18

Using a language that eschews state to try and process the state in a modal editor tickles me.

It doesn't. You can't run a program made of only pure functions. What it does it manage it.

Re: Vim Croquet

#23

Post by weavie » Tue, Jan 28, 2014, 9:53 PM UTC

Looking at the heat map, what does surprise me is how he never uses Escape or ^[. How does he managed to move out of Insert mode? My [ key is starting to wear out due to such heavy use..

Re: Vim Croquet

#24

Post by nbouscal » Tue, Jan 28, 2014, 9:58 PM UTC

weavie wrote: post #23

Looking at the heat map, what does surprise me is how he never uses Escape or ^[. How does he managed to move out of Insert mode? My [ key is starting to wear out due to such heavy use..

He may have it set up the way I do: if I tap Ctrl rather than holding it, it sends Escape. If that's the case, his heatmap might be lumping Escape and Ctrl together.

Re: Vim Croquet

#25

Post by mercurial » Tue, Jan 28, 2014, 9:58 PM UTC

weavie wrote: post #23

Looking at the heat map, what does surprise me is how he never uses Escape or ^[. How does he managed to move out of Insert mode? My [ key is starting to wear out due to such heavy use..

Remapping?

Re: Vim Croquet

#26

Post by nbouscal » Tue, Jan 28, 2014, 10:01 PM UTC

ajanuary wrote: post #18

Using a language that eschews state to try and process the state in a modal editor tickles me.

To elaborate on the other reply, Haskell actually takes a very in-depth and principled approach to managing state. State is necessary for many applications, so rather than eschew it entirely, the idea is to isolate it and make it as explicit as possible. Frequently in complex stateful applications this is done by use of the State monad, with lenses to handle mutation of that state. There's a lot of theory behind it, but in practice it ends up being pretty similar in difficulty level to managing state in more popular languages, just a hell of a lot safer.

Re: Vim Croquet

#27

Post by mercurial » Tue, Jan 28, 2014, 10:04 PM UTC

jbeja wrote: post #14

Even if not related to it and my get some downvoted for saying this. Something that strike me in this post is how cooler haskell code looks vs python.

The nice thing with Haskell is that it can be extremely compact. The problem with Haskell is that it can be extremely compact.

Re: Vim Croquet

#28

Post by Timothee » Tue, Jan 28, 2014, 10:06 PM UTC

weavie wrote: post #23

Looking at the heat map, what does surprise me is how he never uses Escape or ^[. How does he managed to move out of Insert mode? My [ key is starting to wear out due to such heavy use..

I don't know about him but I have 'kj' mapped to . I highly recommend it. (or any variation around it)

Re: Vim Croquet

#29

Post by indiefan » Tue, Jan 28, 2014, 10:12 PM UTC

weavie wrote: post #23

Looking at the heat map, what does surprise me is how he never uses Escape or ^[. How does he managed to move out of Insert mode? My [ key is starting to wear out due to such heavy use..

I use ctrl+c. It's easy to hit than esc, and it's built in, so it always works, even on servers i haven't set my config for, etc.

Re: Vim Croquet

#30

Post by sdegutis » Tue, Jan 28, 2014, 10:33 PM UTC

nathan_long wrote: post #21

Awesome! I'd love to see something like this as a standalone project. "Vim Critic" or "Vim Coach" - something to say "these are the inefficient things you personally do." Probably some low-hanging fruit would be "any keystroke in Normal mode that's repeated." Eg, if I'm doing 'jjjj' to move down or even 'wwww' to hop from word to word, I could be searching or using a movement combo like '4j'.

Personally, the main reason I moved from vim to emacs is because I don't want to have to think about my editor, I want it to be pure muscle memory. I'm okay with hitting "jjjjk" to go 3 lines down rather than trying to guess that it's exactly 3 down and typing "3j". Emacs-style navigating/editing is great for this kind of error-tolerant navigation/editing. It leaves my brain mostly free to focus on whatever I'm actually coding at the time.