nhyatt/putty-source
1
0
Fork 0
mirror of https://git.tartarus.org/simon/putty.git synced 2025-03-22 06:38:37 -05:00
Code Issues Projects Releases Wiki Activity

Jacob's FAQ changes for 0.54.

Browse Source 
[originally from svn r3842]
This commit is contained in:
Simon Tatham 2004-02-10 18:22:00 +00:00
parent b68beb2420
commit f1d532e2d0
1 changed files with 34 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

53
doc/faq.but
View File

@ -1,4 +1,4 @@
\versionid $Id: faq.but,v 1.54 2004/02/04 18:39:14 jacob Exp $ \versionid $Id: faq.but,v 1.55 2004/02/10 18:22:00 simon Exp $
\A{faq} PuTTY FAQ \A{faq} PuTTY FAQ
@ -193,34 +193,45 @@ Porting will become easier once PuTTY has a generalised porting
layer, drawing a clear line between platform-dependent and layer, drawing a clear line between platform-dependent and
platform-independent code. The general intention was for this platform-independent code. The general intention was for this
porting layer to evolve naturally as part of the process of doing porting layer to evolve naturally as part of the process of doing
the first port; a Unix port is now under way and the plan seems to the first port; a Unix port has now been released and the plan
be working so far. seems to be working so far.
\S{faq-ports-general}{Question} What ports of PuTTY exist? \S{faq-ports-general}{Question} What ports of PuTTY exist?
Currently, release versions of PuTTY only run on full Win32 systems. Currently, release versions of PuTTY tools only run on full Win32
This includes Windows 95, 98, and ME, and it includes Windows NT, systems and Unix. \q{Win32} includes Windows 95, 98, and ME, and it
Windows 2000 and Windows XP. In the development code, partial ports includes Windows NT, Windows 2000 and Windows XP.
to Unix (see \k{faq-unix}) and the Mac OS (see \k{faq-mac-port}).
are under way. In the development code, a partial port to the Mac OS (see
\k{faq-mac-port}) is under way.
Currently PuTTY does \e{not} run on Windows CE (see \k{faq-wince}), Currently PuTTY does \e{not} run on Windows CE (see \k{faq-wince}),
and it does not quite run on the Win32s environment under Windows and it does not quite run on the Win32s environment under Windows
3.1 (see \k{faq-win31}). 3.1 (see \k{faq-win31}).
We do not have release-quality ports for any other systems at the We do not have release-quality ports for any other systems at the
present time. If anyone told you we had a Mac port, or an iPaq port, present time. If anyone told you we had an EPOC port, or an iPaq port,
or any other port of PuTTY, they were mistaken. We don't. or any other port of PuTTY, they were mistaken. We don't.
\S{faq-unix}{Question} Will there be a port to Unix? \S{faq-unix}{Question} Is there a port to Unix?
It's currently being worked on. If you look at the nightly source As of 0.54, there are Unix ports of most of the traditional PuTTY
snapshots, you should find a \c{unix} subdirectory, which should tools, and also one entirely new application.
build you Unix ports of Plink, PuTTY itself, PuTTYgen, PSCP, PSFTP,
and also \c{pterm} - an \cw{xterm}-type program which supports the If you look at the source release, you should find a \c{unix}
same terminal emulation as PuTTY. We do not yet have a Unix port of subdirectory containing \c{Makefile.gtk}, which should build you Unix
ports of Plink, PuTTY itself, PuTTYgen, PSCP, PSFTP, and also
\c{pterm} - an \cw{xterm}-type program which supports the same
terminal emulation as PuTTY. We do not yet have a Unix port of
Pageant. Pageant.
If you don't have Gtk, you should still be able to build the
command-line tools.
Note that Unix PuTTY has mostly only been tested on Linux so far;
portability problems such as BSD-style ptys or different header file
requirements are expected.
\S{faq-wince}{Question} Will there be a port to Windows CE or PocketPC? \S{faq-wince}{Question} Will there be a port to Windows CE or PocketPC?
It's currently being worked on, but it's only in its early stages yet, It's currently being worked on, but it's only in its early stages yet,
@ -594,7 +605,7 @@ areas of black space where colour ought to be.
You almost certainly need to enable the \q{Use background colour to You almost certainly need to enable the \q{Use background colour to
erase screen} setting in the Terminal panel. Note that if you do erase screen} setting in the Terminal panel. Note that if you do
this in mid-session, it won't take effect until you reset the this in mid-session, it may not take effect until you reset the
terminal (see \k{faq-resetterm}). terminal (see \k{faq-resetterm}).
\S{faq-resetterm}{Question} When I change some terminal settings, \S{faq-resetterm}{Question} When I change some terminal settings,
@ -607,9 +618,13 @@ send sequences that modify these options in mid-session, but when
the terminal is reset (by server action, or by you choosing \q{Reset the terminal is reset (by server action, or by you choosing \q{Reset
Terminal} from the System menu) the defaults are restored. Terminal} from the System menu) the defaults are restored.
If you want to change one of these options in the middle of a In versions 0.53b and prior, if you change one of these options in
session, you will find that the change does not immediately take the middle of a session, you will find that the change does not
effect. It will only take effect once you reset the terminal. immediately take effect. It will only take effect once you reset
the terminal.
In version 0.54, the behaviour has changed - changes to these
settings take effect immediately.
\S{faq-altgr}{Question} I can't type characters that require the \S{faq-altgr}{Question} I can't type characters that require the
AltGr key. AltGr key.