bug-xboard
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug-XBoard] [bug #27844] Escape sequences in popup messages


From: anonymous
Subject: [Bug-XBoard] [bug #27844] Escape sequences in popup messages
Date: Thu, 29 Oct 2009 07:58:15 +0000
User-agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; GTB6; .NET CLR 1.0.3705; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)

URL:
  <http://savannah.gnu.org/bugs/?27844>

                 Summary: Escape sequences in popup messages
                 Project: XBoard
            Submitted by: None
            Submitted on: Thu Oct 29 07:58:14 2009
                Category: None
                Severity: 3 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any

    _______________________________________________________

Details:

Currently escape sequences in the messages an engine gives with commads like
'telluser' or 'tellusererror' are not recognized, and printed litteraly. As a
consequence, engine authors are now dmanding new tell-like commands for
popping up multi-line message boxes.

Is there any reason not to recognize escape sequences for LF and TAB in such
messages? I would highly prefer that solution over adding (and implementing)
new tell*** commands. I recently noted that XBoard, unlke WinBoard did not
even recognize '\n' as LF in a user-supplied InitString, so that xboard
-firstInitString "new\nrandom\n" actually failed to start the engine! This is
fixed now, but it would be easy to make the same routine that expands the
escapes act on the messages passed by 'telluser' and 'tellusererror' before
displaying them.

H.G. Muller

P.S. what is the intended difference between 'telluser' and 'tellusererror'
anyway? Would it be safe to say (and put it in the protocol specs) that using
'tellusererror' allows the engine then to exit without waiting for 'quit'?
Currently the user gets a double error popup if that happens, one from the
engine, which is then eclipsed by a more cryptic one from XBoard (like "engine
xxx exited unexpectedly: broken pipe").




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?27844>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/





reply via email to

[Prev in Thread] Current Thread [Next in Thread]