Writing an editor in less than 1000 lines of code, just for fun • Hacker News Board

Re: Writing an editor in less than 1000 lines of code, just for fun

#11

Post by edanm » Sun, Jul 10, 2016, 6:38 PM UTC

dwaxe wrote: post #9

savanaly wrote: post #6

Earlier quoted context omitted.

Presumably h, j, k, l will always get you around in vi?

j and k behavior may vary depending on your config.

Everything can vary depending on your config, but unless they were explicitly remapped, j and k should pretty much do the same thing everywhere.

Have you seen somewhere where that isn't the case?

Re: Writing an editor in less than 1000 lines of code, just for fun

#12

Post by ben_jones » Sun, Jul 10, 2016, 6:55 PM UTC

Bonus points for being in C

Re: Writing an editor in less than 1000 lines of code, just for fun

#13

Post by emilong » Sun, Jul 10, 2016, 6:59 PM UTC

This is the kind of magic that got me excited about programming in the first place.

I remember being in high school and one day, after class, a friend of mine mentioned that the best programmer we knew had once written a breakout clone with ANSI "graphics." We found him and he said he didn't have the source any more, but we asked him how he did it. He then proceeded to rewrite the whole thing, in Pascal, in about an hour, this time adding animations. Thanks antirez for bringing back that feeling (and, oh yeah, for redis too ;))

PS. the "Low level terminal handling" is gold here.

Re: Writing an editor in less than 1000 lines of code, just for fun

#14

Post by IshKebab » Sun, Jul 10, 2016, 7:05 PM UTC

savanaly wrote: post #6

elsurudo wrote: post #4

Earlier quoted context omitted.

Nice thing about Nano is that they arrow keys always seem to do what they are supposed to, no matter the system, shell, TTY, etc. Vi seems to have issues sometimes, and needs extra config

Presumably h, j, k, l will always get you around in vi?

Yeah but that is so much less usable. Quick, which one is up?

Re: Writing an editor in less than 1000 lines of code, just for fun

#15

Post by mej10 » Sun, Jul 10, 2016, 7:13 PM UTC

This is great! I love seeing how experienced programmers write small programs like this, especially "from scratch".

Re: Writing an editor in less than 1000 lines of code, just for fun

#16

Post by happyslobro » Sun, Jul 10, 2016, 7:24 PM UTC

dozzie wrote: post #5

elsurudo wrote: post #4

Earlier quoted context omitted.

Nice thing about Nano is that they arrow keys always seem to do what they are supposed to, no matter the system, shell, TTY, etc. Vi seems to have issues sometimes, and needs extra config

I don't know about vi (I think it's still rare on Linux systems), but Vim typically does what is expected from it.

If you ever happen to bork your kernel badly enough to prevent it from booting, you'll find a classic VI pretty quickly, and probably be grateful for it.

Re: Writing an editor in less than 1000 lines of code, just for fun

#17

Post by chongli » Sun, Jul 10, 2016, 7:27 PM UTC

IshKebab wrote: post #14

savanaly wrote: post #6

Earlier quoted context omitted.

Presumably h, j, k, l will always get you around in vi?

Yeah but that is so much less usable. Quick, which one is up?

k of course. Having said that, experienced vi/vim users rarely use jk to get around. Instead we use { } / f etc.

Re: Writing an editor in less than 1000 lines of code, just for fun

#18

Post by Someone » Sun, Jul 10, 2016, 7:31 PM UTC

IshKebab wrote: post #14

savanaly wrote: post #6

Earlier quoted context omitted.

Presumably h, j, k, l will always get you around in vi?

Yeah but that is so much less usable. Quick, which one is up?

Just look at your keyboard :-)

(https://en.m.wikipedia.org/wiki/ADM-3A#Legacy)

I always try to remember them by noting that the leftmost key moves left, the rightmost key moves right (not too hard), and that 'K climbs' (using alliteration to remember that). That leaves 'J' for cursor down.

In practice, though, I use the cursor keys. Luckily, they work on the editors/systems I work on nowadays. Side effect is that I am very bad at remembering those mnemonics.

Re: Writing an editor in less than 1000 lines of code, just for fun

#19

Post by dorfsmay » Sun, Jul 10, 2016, 7:31 PM UTC

IshKebab wrote: post #14

savanaly wrote: post #6

Earlier quoted context omitted.

Presumably h, j, k, l will always get you around in vi?

Yeah but that is so much less usable. Quick, which one is up?

I know k is up, because I constantly k in bash, bit the point of using hjkl is exactly not to know which one is what. You set your finger on the keyboard in home position, now your muscle memory does the rest.

Re: Writing an editor in less than 1000 lines of code, just for fun

#20

Post by 13of40 » Sun, Jul 10, 2016, 7:32 PM UTC

Back in the 90's I took a class in Visual Basic, where one of the assignments was to write a rules-compliant tic-tac-toe game. The teacher apologized for the amount of repetitive code we'd have to write to implement it in Windows forms (or whatever it was called back then). I got it down to one printed page.