So, I made a HUGE mistake the other day when I put xterm-201 into portage. First of all, I hate when people do the straight to stable thing on architectures they know nothing about. So, that means I hate myself this time around.
The other thing is — well, now that xterm has a toolbar, we got requests to be able to enable it. I used to do it off the local USE flag. I decided, instead to just enable its building, but suppress it from automatically showing up when you fire up an xterm. So, I made a little patch, and released into the wild, after having tested it on my box.
Then, I tested some more on my box, and it turns out that a command like this:
xterm -sl 14000 -sb -hold -geometry 150×10+10-30 -title “Camera” -e “time sudo nice -n -10 sudo -u $USER python MYPYTHONAPP.py $*” &
doesn’t actually work. In fact, it doesn’t work at all. Well, the xterm shows up, but it’s all blank. It’s hard to see whether the command in it is actually running, because the xterm is blank, and non-responsive. And trying to terminate those programs is a pain. So, like, I dunno what to do about this — but if someone out there knows, please let me know. I’m rather tempted to hard mask it in 24 hours without input, to be honest. (Though, I am planning on taking my problem to the excellent and brilliant Thomas Dickey and maybe he can guide me through this jungle.
In other news, can you believe Constantine got kicked off? Shocking, when people expected otherwise.
Not that I’m a big fan, or any fan of the guy, but who’s voting for the other two yahoos?
Yup, I just found out the hard way that the new xterm breaks stuff – clusterssh, in my case, which was a huge loss. Into /etc/portage/package.mask for now…
it’s true. xterm-201 it’s broken. not to mention the fact that, at first, alt+backspace didn’t work anylonger and i had to insert the eightBitInput setting into my .Xdefaults file. anyway, this was a quick one. now the big oen: i depend on doing copy/paste from the clipboard (text inserted with xclip) in the xterm console – i really mean “depend”. in the new xterm, the shift+insert combination stopped working – well the buggiest thing was that, it was *sometimes* working (rarely: 3 of 9 xclip “something” + shift/insert steps were working, the others not). i mean, the text *was* in the clipboard (if i did a middle button click, the text was getting pasted in the xterm console), but xterm was refusing to paste it. after about 2 hours of digging, i manually masked it and reemerged the 200-r1 version, which is working.
why don’t i fill any bug? because i personally don’t fill bugs until i get sure that it’s really a bug and not a personal mistake.
Alin, actually, I think it would be nice if you filed me a bug. Then I can just collect all these, and approach Thomas once with all the issues. Ben — I think I will put it in the main package.mask this afternoon, after all.
I’m terribly sorry for all the havoc I’ve wreaked, by the way.
What? Seemant reeks?