Apparently not! The engine can switch it off by printing "kibitz Hello from Crafty", but that is hardly an improvement over sending feature sigint=0...Michel wrote:Is there a way to force xboard not so send SIGINT even if the engine does
not declare sigint=0? This is useful for windows engines.
I guess an option for this is badly needed. Arguably this silly and non-portable feature should even be switched off by default... There once has been talk if there should not be a command-line option to let the user force features as if the egine set them, so you could say -firstFeatures "sigint=0 variants="normal,nocastle"" to trickXBoard into thinking the engine said that. This could be implemented in two flavors, namely altering the default of the mentioned features, or overruling even what the engine says. Perhaps the first flavor would make more sense as a global (non-engine-specific) option, because on a known engine it would either be equivalent to forcing the option (when you know the engine does not send the feature), or it would be overruled (when it does send it). So we could have -featureDefaults for altering defaults, and -firstFeature, -secondFeature for forcing settings (processed after receiving feature done=1).
Anyway, none of this is currently implemented. Note that current XBoards are strictly speaking broken, for a combination of historic reasons and me not properly reading the specs. It sends SIGKILL in stead of SIGTERM to engines that do not promptly react to the quit command, (you can specify a delay, however) and does not pay attention to sigterm=0 for that...
Funny thing is that the (Windows) Joker source does contain the line
Code: Select all
signal(SIGINT, SIG_IGN);
Perhaps I should make a Windows compile of the source I used to make the Linux version (which should be platform independent). This is probably a slightly more modern version (1.1.14h) than the Windows binary I spread around, as it actually is a WB v2 engine implementing setboard (the old one was v1 and did not implement setting up a position at all, but when I made a 10x8 derivative I could not do without that, as 10x8 Chess has several commonly used opening positions, and I then ported that patch back to the 8x8 version.)