1
0
mirror of https://git.tartarus.org/simon/putty.git synced 2025-03-22 14:39:24 -05:00

\n and \r need double backslashes in Halibut.

[originally from svn r4947]
This commit is contained in:
Simon Tatham 2004-12-02 13:48:32 +00:00
parent d46ebde528
commit e83034fe3f

View File

@ -45,10 +45,10 @@ endianness-dependent operations, and so on.
\e{don't} care about. In particular, we expect PuTTY to be compiled \e{don't} care about. In particular, we expect PuTTY to be compiled
on 32-bit architectures \e{or bigger}; so it's safe to assume that on 32-bit architectures \e{or bigger}; so it's safe to assume that
\c{int} is at least 32 bits wide, not just the 16 you are guaranteed \c{int} is at least 32 bits wide, not just the 16 you are guaranteed
by ANSI C. Similarly, we assume that the execution character encoding by ANSI C. Similarly, we assume that the execution character
is a superset of the printable characters of ASCII, though we don't encoding is a superset of the printable characters of ASCII, though
assume the numeric values of control characters, particularly \cw{'\n'} we don't assume the numeric values of control characters,
and \cw{'\r'}.) particularly \cw{'\\n'} and \cw{'\\r'}.)
\H{udp-multi-backend} Multiple backends treated equally \H{udp-multi-backend} Multiple backends treated equally