[Bug-XBoard] [bug #27790] Variant switch not detected

2009-10-24 Thread anonymous
Follow-up Comment #2, bug #27790 (project xboard): Tried that and the variant is recognized now. But as in that manual case I described, the initial board of the observer gets an extra shuffle in all wild variants. The position is repaired after white's first move, though. Apropos FRC - there is

[Bug-XBoard] [bug #27772] Board and holdings out of sync

2009-10-24 Thread anonymous
Follow-up Comment #7, bug #27772 (project xboard): The synchronization seems to work with xboard-4.4.1.20091022. The servers bell code still gets lost in crazyhouse capture moves. ___ Reply to this item at:

[Bug-XBoard] [bug #27772] Board and holdings out of sync

2009-10-24 Thread anonymous
Follow-up Comment #8, bug #27772 (project xboard): I guess the problems are indeed related: WinBoard only sounds bells that are printed to the console. Normally the bells are appended to the prompt, or on an empty line. But I guess when something is captured in crazyhouse, FICS sends the holdings

[Bug-XBoard] [bug #27772] Board and holdings out of sync

2009-10-24 Thread anonymous
Follow-up Comment #9, bug #27772 (project xboard): Sure it can be worked around, but it's normally a good thing to have a closer look to strange behaviour. There could be more serious things behind it. As I see the bell is always sent on a seperate new line just before the board: ^Mfics% ^M gam

[Bug-XBoard] [bug #27772] Board and holdings out of sync

2009-10-24 Thread anonymous
Follow-up Comment #10, bug #27772 (project xboard): Ok, forget about the bell. I saw in the source, that the next prompt after holding gets intentionally suppressed. So there might be a good reason for this. Wouldn't be worth breaking something. So this item can be closed.

[Bug-XBoard] [bug #27772] Board and holdings out of sync

2009-10-24 Thread anonymous
Follow-up Comment #11, bug #27772 (project xboard): Strange! For me the Bell got prefixed to the prompt following the holdings: game 238 white [P] black [N] <- WP 12 15 07fics% 12 15<12> rn--kb-r ... I put in a patch that looks at the matched part when recognizing the prompts after holdings w

[Bug-XBoard] [bug #27772] Board and holdings out of sync

2009-10-24 Thread anonymous
Follow-up Comment #12, bug #27772 (project xboard): Note that the 12 15 and 07 actually stand for lf, cr and bell; the software of this board seems to replace the backslash+0 by a space. ___ Reply to this item at:

[Bug-XBoard] [bug #27790] Variant switch not detected

2009-10-24 Thread anonymous
Follow-up Comment #3, bug #27790 (project xboard): OK, I think I fully understand how it works now. The new game starts with a board, but as the board oof FRC is not recognizably strange, you stay in VariantNormal. (That it is not the regular opening position is no clue, as there are many wilds w

[Bug-XBoard] [bug #27772] Board and holdings out of sync

2009-10-24 Thread anonymous
Follow-up Comment #13, bug #27772 (project xboard): I used "telnet freechess.org|tee log.txt" to capture the strings (manually setting style 12). I don't know, if that's a proper way. The whole beep-thing was more to make sure, that a character isn't overwritten by accident, so that "bell 0" woul

[Bug-XBoard] [bug #27772] Board and holdings out of sync

2009-10-24 Thread anonymous
Follow-up Comment #14, bug #27772 (project xboard): Well, it seems that for me, the bell character is almost always prefixed to the prompt. I captured it from the winboard.debug file, but that should not really matter. It might be that there is a kind of race condition in the server, where two me

[Bug-XBoard] [bug #27772] Board and holdings out of sync

2009-10-24 Thread anonymous
Follow-up Comment #15, bug #27772 (project xboard): Bell() -> RingBell() Works now. ___ Reply to this item at: ___ Message sent via/by Savannah ht

[Bug-XBoard] [bug #27772] Board and holdings out of sync

2009-10-24 Thread anonymous
Follow-up Comment #16, bug #27772 (project xboard): Yeah, that was the nasty part. RingBell() strangely enough is the move sound in WinBoard, and there is no way to call the sound produced by the bell charactr from the back-end. Only the front-end routine that sends text to the console produces i

[Bug-XBoard] [bug #27799] fix for nested-nested-nested variations

2009-10-24 Thread anonymous
URL: Summary: fix for nested-nested-nested variations Project: XBoard Submitted by: None Submitted on: Sat Oct 24 16:51:30 2009 Category: None Severity: 3 - Normal

[Bug-XBoard] [bug #27799] fix for nested-nested-nested variations

2009-10-24 Thread anonymous
Follow-up Comment #1, bug #27799 (project xboard): Not sure I understand the lex syntax completely. The "+", is that a meta character for one or more, like "*" means zero or more times, and "?" means one or zero? And unescaped parentheses group these operators? Btw, now that I look at parser.l,

[Bug-XBoard] [bug #27772] Board and holdings out of sync

2009-10-24 Thread anonymous
Follow-up Comment #17, bug #27772 (project xboard): I guess I found a front-end-independent fix: In stead of RingBell() or my new routine Bell(), simply call: SendToPlayer(" 07", 1); This sends a bell to the console, which both in WinBoard and XBoard produces the required sound! :-D H.G. Mull

[Bug-XBoard] [bug #27772] Board and holdings out of sync

2009-10-24 Thread anonymous
Follow-up Comment #18, bug #27772 (project xboard): That prompt suppressing reminds me of all those "fics%" lines filling up the xterm-console while playing (each opponent's move adds one). Might be further filter candidates. ___ Reply to

[Bug-XBoard] [bug #27772] Board and holdings out of sync

2009-10-24 Thread anonymous
Follow-up Comment #19, bug #27772 (project xboard): I think those are exactly the prompts that are filtered here. Strange that this does not work for XBoard: the filtering takes place in the back-end. In WinBoard you don't get such prompts, and the console stays nicely empty. H.G. Muller __

[Bug-XBoard] [bug #27153] Pre-move does not work on xboard 4.4beta1

2009-10-24 Thread anonymous
Follow-up Comment #16, bug #27153 (project xboard): OK, finally got some time to test, built xboard-4.4.1.20091019, and indeed it seems the issue is now fixed. As a side note, there seem to be some lingering debug messages in that version (backend.c at line 3429) as xboard outputs the following