Why so bitter? Because the fucking morons that "enhanced" xterm committed the cardinal sin of software development - they introduced incompatible changes into xterm while pretending like they're perfectly compatible. So people that have settings for years that have worked with xterms find that they no longer work with xterms.
In fairness, it's not really the xterm that's incompatible, it's the xterm descriptions that ship with modern operating systems that are incompatible with older xterms. But that's a ridiculous dodge. The developers had to know that people would actually USE the cool new features they put into xterms. And by so doing, create termcap/terminfo descriptions that are not compatible. Old xterm descriptions are compatible with new xterms but not vice-versa. In other words, these morons created a system that when put into use would be forward-compatible, not backward-compatible. It's insane.
Let me be clear - creating a new terminal is great, but it should never have been called an xterm. Now when I log in from an old system to a new system, and my TERM variable is forwarded, suddenly "xterm" is wrong, even though it was right on the original system, and I have to tell the new system that my terminal is actually an "xterm-r6" (even though there IS no such thing). But I can't automate that, because if I'm coming from a new system, I may want those new features, and there's no automated way to differentiate.
The new xterm shoulda been "xtermplus" or something. Die, die, die you idiots. Die and go to hell and spend all of eternity using incompatible xterms.
So again, you log into the new system and tell it you have an xterm (because in fact, you DO have an xterm), and you read a man page or use "less" or "more", and it porks things all to hell and gone, because xterm developers are a bunch of moronic mother-fuckers that I'd recommend lobotomizing, if that hadn't apparently already been done.
If they had at least done that, then the login process could check the xterm features or version, and set the TERM variable appropriately. It'd be an ugly hack over a really bad idea from a bunch of fucks that shoulda known better. But an ugly hack is better than no hack at all.
So that's how incredibly stupid, dumb, blind, moronic, incompetent, worthless, and crappy these so-called developers are. Am I making myself clear hear?
The problem is that on traditional two-color (foreground/backround) xterms, you have two color highlighting, a.k.a. reverse-video. And by conincidence traditional xterms makes a cursor using reverse-video highlighting. So the matching bracket or whatever gets reverse-video highlighted, and the cursor gets reverse-video highlighted TWICE, which means once to reverse video and once again back to normal, so apparently the real cursor simply disappears, meanwhile, something else that looks EXACTLY like a cursor, appears somewhere else entirely. The effect is that you're moving your cursor around, and the cursor acts like a drunk fucker, or to put it another way, almost as stupid as xterm and vim developers.
The solution? Line 'em up along with the xterm developers. At a more practical level, you'd think ":se nosm", or ":set noshowmatch". Well, these may work in some versions but not others. For me, ":NoMatch" did it.
Add a comment
|My Home||Professional Home||TomSaraZac Home||Work Email|