Bug#445441: clusterssh: Doesnt work with slightly different xterm settings
Package: clusterssh Version: 3.19.1-8 Severity: normal While clusterssh has a .csshrc where you can set terminal_args= in it - it breaks if you actually do that. Like - try adding -class SOMETHING to give your xterms another class (so loading other default options), you end up with all the terminal windows as expected - but are unable to do anything with them. You can type directly into one of the windows, but the cssh control window isnt able to deal with any of them. -- bye Joerg Von einem Besucher auf dem LT: Die 3 Microsoft-Leute auf Ihrem Stand müssen sich vorkommen wie 3 Mönche im Puff. pgpy0d3D9oMC7.pgp Description: PGP signature
Bug#445441: clusterssh: Doesnt work with slightly different xterm settings
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 If you are going to set the class to something other than the default, try updating terminal_allow_send_events in your .csshrc to be: -xrm '$class.VT100.allowSendEvents:true or just: -xrm '*.VT100.allowSendEvents:true (Which is the default starting with 3.19.1-8, but the value -xrm 'XTerm.VT100.allowSendEvents:true' may have already be in your .csshrc.) clusterssh depends on allowSendEvents to be set in order to send events to the terminal windows. In general, options should work with terminal_args. -class is a little special. If you think it occurs commonly, I could suggest a patch to upstream that picks up the class value and automatically places in the -xrm string. Cheers, Tony Joerg Jaspert wrote: Package: clusterssh Version: 3.19.1-8 Severity: normal While clusterssh has a .csshrc where you can set terminal_args= in it - it breaks if you actually do that. Like - try adding -class SOMETHING to give your xterms another class (so loading other default options), you end up with all the terminal windows as expected - but are unable to do anything with them. You can type directly into one of the windows, but the cssh control window isnt able to deal with any of them. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHBrNPpdwBkPlyvgMRAq14AJ4/vJkZ+ShYc47Qmdxg8479nUXPowCdGWlT SvKjEZ8f+nyobv0YQZr0sZs= =obIQ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#445441: clusterssh: Doesnt work with slightly different xterm settings
On 11163 March 1977, tony mancill wrote: If you are going to set the class to something other than the default, try updating terminal_allow_send_events in your .csshrc to be: -xrm '$class.VT100.allowSendEvents:true Doesnt work. or just: -xrm '*.VT100.allowSendEvents:true Works. (Which is the default starting with 3.19.1-8, but the value -xrm 'XTerm.VT100.allowSendEvents:true' may have already be in your .csshrc.) Yes, and I completly missed that. In general, options should work with terminal_args. -class is a little special. If you think it occurs commonly, I could suggest a patch to upstream that picks up the class value and automatically places in the -xrm string. Well. Commonly, i dont know. I just want to load different settings for cssh terminal windows than i want for all my usual terminal windows, so I have a few entries in .Xdefaults that I load with xrdb. There one needs such things. It sure would be nice if cssh does understand that by default, but if you have *. in -xrm anyway, then it should be enough. Your call, as its your time. Feel free to take this bug as a tracking point for the patch or close it if you dont want to do the work, the workaround with the -xrm is fine for me. -- bye Joerg liw we have release cycles, that's why it takes so long to get a release out; if we had release race cars, things would go a lot faster pgptDdfhUoyB6.pgp Description: PGP signature
