pterm(1) | PuTTY tool suite | pterm(1) |
pterm ‐ yet another X terminal emulator
pterm [ options ]
pterm is a terminal emulator for X. It is based on a port of the terminal emulation engine in the Windows SSH client PuTTY.
The command-line options supported by pterm are:
pterm -e sh -c 'mycommand < inputfile'
Any character set name which is valid in a MIME header (and supported by pterm) should be valid here (examples are `ISO-8859-1', `windows-1252' or `UTF-8'). Also, any character encoding which is valid in an X logical font description should be valid (`ibm-cp437', for example).
pterm's default behaviour is to use the same character encoding as its primary font. If you supply a Unicode (iso10646-1) font, it will default to the UTF-8 character set.
Character set names are case-insensitive.
pterm -xrm 'ScrollbarOnLeft: 1'
pterm can be more completely configured by means of X resources. All of these resources are of the form pterm.FOO for some FOO; you can make pterm look them up under another name, such as xyz.FOO, by specifying the command-line option `-name xyz'.
When this setting is set to 1, pterm will close immediately if the process exits cleanly (with an exit status of zero), but the window will stay around if the process exits with a non-zero code or on a signal. This enables you to see what went wrong if the process suffers an error, but not to have to bother closing the window in normal circumstances.
This feature is a POTENTIAL SECURITY HAZARD. If a malicious application can write data to your terminal (for example, if you merely cat a file owned by someone else on the server machine), it can change your window title (unless you have disabled this using the NoRemoteWinTitle resource) and then use this service to have the new window title sent back to the server as if typed at the keyboard. This allows an attacker to fake keypresses and potentially cause your server-side applications to do things you didn't want. Therefore this feature is disabled by default, and we recommend you do not turn it on unless you really know what you are doing.
The bell overload mode is activated by receiving N bells in time T; after a further time S without any bells, overload mode will turn itself off again.
Bell overload mode is always deactivated by any keypress in the terminal. This means it can respond to large unexpected streams of data, but does not interfere with ordinary command-line activities that generate beeps (such as filename completion).
Colours 0 and 1 specify the foreground colour and its bold equivalent (the -fg and -bfg command-line options). Colours 2 and 3 specify the background colour and its bold equivalent (the -bg and -bbg command-line options). Colours 4 and 5 specify the text and block colours used for the cursor (the -cfg and -cbg command-line options). Each even number from 6 to 20 inclusive specifies the colour to be used for one of the ANSI primary colour specifications (black, red, green, yellow, blue, magenta, cyan, white, in that order); the odd numbers from 7 to 21 inclusive specify the bold version of each colour, in the same order. The defaults are:
pterm.Colour0: 187,187,187 pterm.Colour1: 255,255,255 pterm.Colour2: 0,0,0 pterm.Colour3: 85,85,85 pterm.Colour4: 0,0,0 pterm.Colour5: 0,255,0 pterm.Colour6: 0,0,0 pterm.Colour7: 85,85,85 pterm.Colour8: 187,0,0 pterm.Colour9: 255,85,85 pterm.Colour10: 0,187,0 pterm.Colour11: 85,255,85 pterm.Colour12: 187,187,0 pterm.Colour13: 255,255,85 pterm.Colour14: 0,0,187 pterm.Colour15: 85,85,255 pterm.Colour16: 187,0,187 pterm.Colour17: 255,85,255 pterm.Colour18: 0,187,187 pterm.Colour19: 85,255,255 pterm.Colour20: 187,187,187 pterm.Colour21: 255,255,255
Most of the X resources have silly names. (Historical reasons from PuTTY, mostly.)
2004‐03‐24 | PuTTY tool suite |