All talks about bugs, how they were solved, dead ends attempted, tools/techniques used to diagnose, etc.
Would be really useful to see how other people approach debugging and you'd probably get to learn about lots of tools you didn't know existed.
Good debugging stories, like the OP, are mysteries.
By the way, as I understand, one shouldn't fiddle with &t_* options, unless strictly necessary. It's supposed to be a Bad Idea ® because it makes things less portable.
(Although I'm also guilty of this, changing the cursor color in insert mode is just too cool for me to resist).
Test Words Go Here
Test Words Got Here
The first thing I do when I encounter a problem in vim is to run it a) without plugins, b) without my .vimrc, and c) with neither plugins nor rc.
I swear I should just have a sticky with that on my monitor. Would really save me a lot of time.
Anyone who reads the part where t_F9 actually means F19 and doesn't get completely enraged at the person who made that decision never gets to work for me...
I like her way of thinking and would probably get along with her if I were to meet her.
This read like a tech version of a Scooby Doo episode.
A great mystery solved with a little symlink.
2. Waste hours of your and other's time chasing the weird "bug" that's direct consequence of point 1.
3. Write a long pointless post where you don't even aknowledge your initial stupidity.
4. Get famous on the World Wide Web.
No fucking wonder why nobody RTFM anymore: failure is success!
Honestly, if you are not impressed by this piece of bug hunting, you are either an absolute genius, or someone without enough experience to appreciate just how difficult what she accomplished actually was (note the elegance of the solution - simply applying a symbolic link). I'm going to go with option 2, because I would already know who you are if it was option 1, but I don't, you're an anonymous internet 'nym.
No, I'm not impressed.
I'm not impressed because the "bug" she wasted so much time to hunt down is not a vim or tmux bug at all. Even with quotes around "bug".
It's someone, somewhere, failing to read the aforelinked 42 lines long README.
Nothing to write home about.