3 ms·
Replying to myself because I can't seem to reply to sigzero: Yeah, I definitely need to get around to reading :h filetype. I mentioned Snipmate in the article
by stevelosh 16y ago
Replying to myself because I can't seem to reply to sigzero:
Yeah, I definitely need to get around to reading :h filetype.
I mentioned Snipmate in the article, so I know about it :)
- icey 16y agoHN has a speed-limiter in place to prevent flamefests. If you find yourself in the position of not being able to reply due to the previous comment being made too recently, you can click the "link" link and reply on the resulting page.
- stevelosh 16y agoAh, neat, I didn't know that. Thanks!
- samdk 16y agoThis is not vim-related, but the reason you couldn't reply is that HN doesn't let you reply to a comment until after a certain amount of time has passed. This amount of time depends on how deep the comment is in the tree. (I believe the restriction is there to help prevent excessively deep comment trees that are just people arguing back and forth.)
- stevelosh 16y agoCool, thanks! It would be helpful if it mentioned that somewhere...
- stevelosh 16y agoAddendum: ugh, it's not even in the damn FAQ.
- dasil003 16y agoThat's because it's inside information.
- paulbaumgart 16y agoIt was announced here: http://ycombinator.com/newsnews.html http://ycombinator.com/newsnews.html
- _delirium 16y agoIt's circumventable, as well; if there's no "reply" link on the main threaded view, you can click the "link" button to get the comment on its own page, and reply from there.
- sigzero 16y agoI just started using it. Like it a lot.