mirror of
https://git.tartarus.org/simon/putty.git
synced 2025-04-14 01:28:06 -05:00
6155365076
"server:fixed" was a good default when GTK1 was common and non-X11 environments were rare. Now it's the other way round - Wayland is very common and the GTK1 configuration of PuTTY is legacy - so it's time to make the default GTK font a client-side one. Of course, anyone with an existing saved session (including Default Settings) won't be affected by this change; it only helps new users without an existing ~/.putty at all. That's why we _also_ need the fallbacks introduced by the previous couple of commits. But we can at least start making it sensible for new users. (I considered keeping the #if, and switching it round so that it tests GTK_CHECK_VERSION(2,0,0) rather than NOT_X_WINDOWS, i.e. selects the client-side default whenever client-side fonts _are_ available, instead of only when server-side fonts _aren't_. That way, in GTK1 builds, the Conf default font would _still_ be "server:fixed". But I think this is firstly too marginal to worry about, and secondly, it's more futureproof to make the default the same everywhere: if anyone still stuck on a GTK1 environment later manages to update it, then their saved settings are less likely to have had a legacy thing written into them. And the GTK1 build will still run out of the box because of the last-ditch fallback mechanism I've just added.)
PuTTY source code README
========================
This is the README for the source code of PuTTY, a free Windows and
Unix Telnet and SSH client.
PuTTY is built using CMake <https://cmake.org/>. To compile in the
simplest way (on any of Linux, Windows or Mac), the general method is
to run these commands in the source directory:
cmake .
cmake --build .
These commands will expect to find a usable compile toolchain on your
path. So if you're building on Windows with MSVC, you'll need to make
sure that the MSVC compiler (cl.exe) is on your path, by running one
of the 'vcvars32.bat' setup scripts provided with the tools. Then the
cmake commands above should work.
To install in the simplest way on Linux or Mac:
cmake --build . --target install
On Unix, pterm would like to be setuid or setgid, as appropriate, to
permit it to write records of user logins to /var/run/utmp and
/var/log/wtmp. (Of course it will not use this privilege for
anything else, and in particular it will drop all privileges before
starting up complex subsystems like GTK.) The cmake install step
doesn't attempt to add these privileges, so if you want user login
recording to work, you should manually ch{own,grp} and chmod the
pterm binary yourself after installation. If you don't do this,
pterm will still work, but not update the user login databases.
Documentation (in various formats including Windows Help and Unix
`man' pages) is built from the Halibut (`.but') files in the `doc'
subdirectory. If you aren't using one of our source snapshots,
you'll need to do this yourself. Halibut can be found at
<https://www.chiark.greenend.org.uk/~sgtatham/halibut/>.
The PuTTY home web site is
https://www.chiark.greenend.org.uk/~sgtatham/putty/
If you want to send bug reports or feature requests, please read the
Feedback section of the web site before doing so. Sending one-line
reports saying `it doesn't work' will waste your time as much as
ours.
See the file LICENCE for the licence conditions.