•
3.1.3.1 The PuTTY Event Log
•
3.1.3.2 Special commands
•
3.1.3.3 Starting new sessions
•
3.1.3.4 Changing your session settings
•
3.1.3.5 Copy All to Clipboard
•
3.1.3.6 Clearing and resetting the terminal
•
3.1.3.7 Full screen mode
3.1.3.1 The PuTTY Event Log
If you choose ‘Event Log’ from the system menu, a small window will pop up in which PuTTY logs significant events during the connection. Most of the events in the log will probably take place during session startup, but a few can occur at any point in the session, and one or two occur right at the end.
You can use the mouse to select one or more lines of the Event Log, and hit the Copy button to copy them to the clipboard. If you are reporting a bug, it's often useful to paste the contents of the Event Log into your bug report.
3.1.3.2 Special commands
Depending on the protocol used for the current session, there may be a submenu of ‘special commands’. These are protocol-specific tokens, such as a ‘break’ signal, that can be sent down a connection in addition to normal data. Their precise effect is usually up to the server. Currently only Telnet, SSH, and serial connections have special commands.
The ‘break’ signal can also be invoked from the keyboard with Ctrl-Break.
The following special commands are available in Telnet:
•Are You There
•Break
•Synch
•Erase Character
PuTTY can also be configured to send this when the Backspace key is pressed; see
section 4.16.3
.
•Erase Line
•Go Ahead
•No Operation
Should have no effect.
•Abort Process
•Abort Output
•Interrupt Process
PuTTY can also be configured to send this when Ctrl-C is typed; see
section 4.16.3
.
•Suspend Process
PuTTY can also be configured to send this when Ctrl-Z is typed; see
section 4.16.3
.
•End Of Record
•End Of File
In an SSH connection, the following special commands are available:
•IGNORE message
Should have no effect.
•Repeat key exchange