And now I've discovered that vim spell check skips words with leading markdown symbols like `*randical`. I'll have to dig into that more.
Update: pasting the web page to Google Docs found a few more typos. I fixed those, too. Usually I print and read to find typos, maybe I skipped that this time. Good reminder to do that and the Gdocs review. Really: thanks for the reminder, regardless of the sassiness. :-)
I really am sorry for being a troll and writing the kind of comment that bums me out on a regular basis. This seems like a good post and a good discussion.
It can just be frustrating for those of us that have a hard time getting traction when we post projects etc on sites like HN. It can manifest into petty toxic behavior especially in comment sections.
In the words of Paul Doherty... "I'll do better next time."
> And now I've discovered that vim spell check skips words with leading markdown symbols like `*randical`. I'll have to dig into that more.
Taking a quick look, for me it seems that (Neo)Vim spell check skips anything in italics or bold. No highlights whatsoever anywhere in that region. Definitely not something you want to realize _after_ publishing articles!
Edit: Considering the comment about using :syn off, seems like this is probably a conflict of some kind with the way Vim actually italicizes/bolds things in terminals that support it, now.
Anything longer than a few sentences I'll write in vim and am always horrified when I copy to Gmail or Google docs and find spelling mistakes, duplicated words, and incomplete sentences everywhere.
And now I've discovered that vim spell check skips words with leading markdown symbols like `*randical`. I'll have to dig into that more.
Update: pasting the web page to Google Docs found a few more typos. I fixed those, too. Usually I print and read to find typos, maybe I skipped that this time. Good reminder to do that and the Gdocs review. Really: thanks for the reminder, regardless of the sassiness. :-)