mirror of
https://git.tartarus.org/simon/putty.git
synced 2025-01-25 01:02:24 +00:00
5f2eff2fea
This was requested by a downstream of the code, who wanted to change the time/space tradeoff in the terminal. I currently have no plans to change this setting for upstream PuTTY, although there is a cmake option for it just to make testing it easy. To avoid sprinkling ifdefs over the whole terminal code, the strategy is to keep the separate type 'compressed_scrollback_line', and turn it into a typedef for a 'termline *'. So compressline() becomes almost trivial, and decompressline() even more so. Memory management is the fiddly part. To make this work sensibly on both sides, I've broken up each of compressline() and decompressline() into two versions, one of which takes ownership of (and logically speaking frees) its input, and the other doesn't. So at call sites where a function was followed by a free, it's now calling the 'and_free' version of the function, and where the input object was reused afterwards, it's calling the 'no_free' version. This means that in different branches of the #if, I can make one function call the other or vice versa, and no call site is stuck with having to do things in a more roundabout way than necessary. The freeing of the _return_ value from decompressline() is handled for us, because termlines already have a 'temporary' flag which is set when they're returned from the decompressor, and anyone receiving a termline from lineptr() calls unlineptr() when they're finished with it, which will _conditionally_ free it, depending on that 'temporary' flag. So in the new mode, 'temporary' is never set at all, and all those unlineptr() calls do nothing. However, we also still need to free compressed lines properly when they're actually being thrown away (scrolled off the top of the scrollback, or cleaned up in term_free), and for that, I've made a new special-purpose free_compressed_line() function. |
||
---|---|---|
charset | ||
cmake | ||
contrib | ||
crypto | ||
doc | ||
icons | ||
keygen | ||
otherbackends | ||
proxy | ||
ssh | ||
stubs | ||
terminal | ||
test | ||
unicode | ||
unix | ||
utils | ||
windows | ||
.gitignore | ||
aqsync.c | ||
be_list.c | ||
Buildscr | ||
Buildscr.cv | ||
callback.c | ||
cgtest.c | ||
CHECKLST.txt | ||
clicons.c | ||
CMakeLists.txt | ||
cmdgen.c | ||
cmdline.c | ||
config.c | ||
console.c | ||
console.h | ||
defs.h | ||
dialog.c | ||
dialog.h | ||
errsock.c | ||
import.c | ||
LATEST.VER | ||
ldisc.c | ||
LICENCE | ||
licence.pl | ||
logging.c | ||
marshal.h | ||
misc.h | ||
mksrcarc.sh | ||
mkunxarc.sh | ||
mpint.h | ||
network.h | ||
pageant.c | ||
pageant.h | ||
pinger.c | ||
pscp.c | ||
psftp.c | ||
psftp.h | ||
psftpcommon.c | ||
psocks.c | ||
psocks.h | ||
putty.h | ||
puttymem.h | ||
README | ||
release.pl | ||
settings.c | ||
sign.sh | ||
ssh.h | ||
sshcr.h | ||
sshkeygen.h | ||
sshpubk.c | ||
sshrand.c | ||
storage.h | ||
timing.c | ||
tree234.h | ||
version.h | ||
x11disp.c |
This is the README for 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), run these commands in the source directory: cmake . cmake --build . Then, 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.