Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Vim's 400 line function to wait for keyboard input

geoff.greer.fm

Post reply on HN
Print view View original

221–230 of 239 posts

Re: Vim's 400 line function to wait for keyboard input

#221

Post by ggreer »

roghummal wrote: post #213
ggreer wrote: post #211

Earlier quoted context omitted.

I'm sorry if you thought the post was self-serving. I can only say with sincerity that it wasn't. I have no motive beyond my interest in software. If you don't believe my claim of selflessness, believe my claim of competence: If I was trying to build a personal brand, I could do much better than delving into Vim's codebase for a one-off snippet. It's not difficult to create insubstantial content that is widely-shared…

You delved[1] into the vim source and found this. You offered no solution except to use neovim, which happens to be 'supported' by the /amazing/ company you're the CEO of. You're very well practiced in false modesty and apologies but fuck you; I'm not sure you know what sincerity means. I'm sorry if I don't think you're being sincere. Let's have a drink sometime! Let's network! 1. Anything as old as vim, continuously…

Judging from this comment and others, you seem uninterested in civility or truth. I doubt anything can change your mind on this issue.

Still, others read these comments, so I feel compelled to offer corrections: 18 months ago, I pledged $50 to Neovim's Bountysource. My company has not contributed a cent to Neovim. We maintain plugins for many text editors, including Vim and Neovim. That's it.

You keep slinging mud, but there is no ulterior motive at work here. I urge you to treat people more charitably in the future.

Re: Vim's 400 line function to wait for keyboard input

#222

Post by Spakman »

I suppose it's because I've spent quite a lot of time in the GNU Readline source that this function doesn't seem that bad. Not that I'm wanting to endorse it as great code, of course.

I find it fascinating to look at how old but very well used software develops (often, but not always) in ways that seem completely ghastly.

Re: Vim's 400 line function to wait for keyboard input

#223

Post by roghummal »

ggreer wrote: post #219
roghummal wrote: post #217

Earlier quoted context omitted.

If you're ever in the Silicon Valley we should "meet up". I'll be nicer to you but you're buying.

>>I don’t consider myself very devoted to my work, but >Don't try and pretend your problems are our problems. Struggling to survive, scrap by scrap. Fuck off. If you're ever in the Silicon Valley we should "meet up". I'll be nicer to you. You trawled through my writings to find one sentence in one blog post[1] to voice outrage at. I'm not sure how to react to that. I guess... congratulations on your hard work. I live…

So I don't confuse you with an edit and for my own gratification, I'd like you to know that I didn't 'trawl' through your posts to find something that supported mine.

Your titles are bait. Their substance is minimal. When you've had something to say it has been said before, better. If you care about the code as much as you claim you should let it go. (I'm questioning this last statement.)

You're a natural born CEO. Find your Woz.

Edit: And then someone to run your company. (I just saw "Judging from this comment and others, you seem uninterested in civility or truth. I doubt anything can change your mind on this issue.")

Re: Vim's 400 line function to wait for keyboard input

#224

Post by roghummal »

ggreer wrote: post #221
roghummal wrote: post #213

Earlier quoted context omitted.

You delved[1] into the vim source and found this. You offered no solution except to use neovim, which happens to be 'supported' by the /amazing/ company you're the CEO of. You're very well practiced in false modesty and apologies but fuck you; I'm not sure you know what sincerity means. I'm sorry if I don't think you're being sincere. Let's have a drink sometime! Let's network! 1. Anything as old as vim, continuously…

Judging from this comment and others, you seem uninterested in civility or truth. I doubt anything can change your mind on this issue. Still, others read these comments, so I feel compelled to offer corrections: 18 months ago, I pledged $50 to Neovim's Bountysource. My company has not contributed a cent to Neovim. We maintain plugins for many text editors, including Vim and Neovim. That's it. You keep slinging mud, b…

Civility works best with mutual respect. That respect might be hollow or fleeting but it's established and traded on. When two people meet for the first time there's a credit exchanged. That's the humanity-freebie.

Don't ask for sympathy ("They don't want civility or truth!!!"), ask yourself why you were treated "uncivilized".

Truth? I suspect that's a glitch in translation.

Re: Vim's 400 line function to wait for keyboard input

#225

Post by jrbrtsn »

omaranto wrote: post #129
jrbrtsn wrote: post #126

Earlier quoted context omitted.

Most likely you've typed Ctrl-S, which causes the terminal to pause. Here is the what the vim docs have to say about that: Note: CTRL-S does not work on all terminals and might block further input, use CTRL-Q to get going again.

I've never heard of Ctrl-S causing a crash, though. So your explanation at most accounts for the hangs.

I've used vim pretty much every work day in the last 15 years or so, and I can count the number of times it's crashed on one hand. If you can actually verify that it crashed (i.e. core dump file), then you've got the source available, and you can send in the patch.

Re: Vim's 400 line function to wait for keyboard input

#226

Post by wtbob »

brudgers wrote: post #73
rando3826 wrote: post #69

Emacs C code is far better! And it's only ~22% c code instead of vim's ~66% reference: https://www.openhub.net/p/vim https://www.openhub.net/p/emacs

Vim or Emacs, either is fine. So is Eclipse. Etc.

> Vim or Emacs, either is fine.

True enough.

> So is Eclipse.

No, Eclipse must be killed with fire.

Re: Vim's 400 line function to wait for keyboard input

#227

Post by knodi123 »

im3w1l wrote: post #209
knodi123 wrote: post #114

Earlier quoted context omitted.

I remember I once went to great trouble to use a succession of old computers to copy my favorite DOS game off of a 5 1/4" floppy into a 3 1/2" floppy, and then from there onto a network, and then onto my laptop, so I could take it to school with me. And in the end, I learned that the game ran so fast on my laptop that your character would move at light speed and then die as soon as you pressed a button, because my la…

If you still want to play it, dosbox supports adjusting emulation speed.

I kinda do, actually. maybe I will.

It was this game if you're curious: http://www.dosgamesarchive.com/download/the-black-cauldron/

Re: Vim's 400 line function to wait for keyboard input

#228

Post by omaranto »

jrbrtsn wrote: post #225
omaranto wrote: post #129

Earlier quoted context omitted.

I've never heard of Ctrl-S causing a crash, though. So your explanation at most accounts for the hangs.

I've used vim pretty much every work day in the last 15 years or so, and I can count the number of times it's crashed on one hand. If you can actually verify that it crashed (i.e. core dump file), then you've got the source available, and you can send in the patch.

It's never crashed on me. I'm not the person who claimed it crashed.

Re: Vim's 400 line function to wait for keyboard input

#229

Post by Watabou »

mintplant wrote: post #205
Watabou wrote: post #185

Earlier quoted context omitted.

Do you also blame Microsoft Word because it doesn't let you play movies?

People have tried to add async plugin support to vim, but the patches have all been rejected. Meanwhile, the plugin support in Neovim is worlds better. Microsoft Word doesn't even accept patches, which I do indeed hold against it.

The patches were rejected because they didn't provide a working solution for cross platform support. The plugin system in Neovim is only "better" for people who actually want async plugins. I am not one of them.

Re: Vim's 400 line function to wait for keyboard input

#230

Post by plorkyeran »

JupiterMoon wrote: post #215
msravi wrote: post #194

Earlier quoted context omitted.

Right. So you recommend neovim, which is good, except that it won't install -- not on some unused OS, but on OS X 10.6.8 (Snow Leopard). Now I know that's a little behind, but really? Beautiful code that won't work on a 2010 OS is just awesome. As an aside, I think it's a growing problem that the formulae in Homebrew are not updated to support 10.6.8. And Vim? It just works. Maybe it's all those #ifdefs that make the…

Do Apple supply security updates for Snow Leopard still?

Apple doesn't even supply security updates for 10.9 anymore.
Post reply on HN