nhyatt/putty-source
1
0
Fork 0
mirror of https://git.tartarus.org/simon/putty.git synced 2025-07-02 03:52:49 -05:00
Code Issues Projects Releases Wiki Activity

Further documentation work. Tidy up the Config chapter (add a few

Browse Source 
new features - the code had got ahead of the docs), and propagate a
couple of cross-references to other files as a result.

[originally from svn r1424]
This commit is contained in:
Simon Tatham
2001-11-25 19:22:47 +00:00
parent fe943dcd68
commit 7e0ef0b253
3 changed files with 206 additions and 160 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
doc/faq.but
View File

@ -1,4 +1,4 @@
\versionid $Id: faq.but,v 1.11 2001/11/25 16:57:45 simon Exp $
\versionid $Id: faq.but,v 1.12 2001/11/25 19:22:47 simon Exp $
\A{faq} PuTTY FAQ
@ -556,7 +556,7 @@ try harder to keep connections alive instead of abandoning them.
\S{faq-puttyputty}{question} When I \cw{cat} a binary file, I get
`PuTTYPuTTYPuTTY' on my command line.
Don't \cw{cat} binary files, then.
Don't do that, then.
This is designed behaviour; when PuTTY receives the character
Control-E from the remote server, it interprets it as a request to
@ -567,10 +567,15 @@ response. Writing a binary file to your terminal is likely to output
many Control-E characters, and cause this behaviour. Don't do it.
It's a bad plan.
To mitigate the effects, you could configure the answerback string
to be empty (see \k{config-answerback}); but writing binary files to
your terminal is likely to cause various other unpleasant behaviour,
so this is only a small remedy.
\S{faq-puttyputty}{question} When I \cw{cat} a binary file, my
window title changes to a nonsense string.
Don't \cw{cat} binary files, then.
Don't do that, then.
It is designed behaviour that PuTTY should have the ability to
adjust the window title on instructions from the server. Normally