mirror of
https://git.tartarus.org/simon/putty.git
synced 2025-04-09 15:18:06 -05:00
f2d63388a8
When telling front ends to paint the screen, the terminal code treats the cursor as an attribute applied to the character cell(s) it appears in. do_paint() detects changes to most such attributes by storing what it last sent to the front end in term->disptext and comparing that with what it thinks should be displayed in the window. However, before this commit the cursor was special. Its last-drawn position was recorded in special structure members and invalidated parts of the display based on those. The cursor attributes were treated as "temporary attributes" and were not saved in term->disptext. This commit regularizes this and turns the cursor attributes into normal attributes that are stored in term->disptext. This removes a bunch of special-case code in do_paint() because now the normal update code handles the cursor properly, and also removes some members from the Terminal structure. I hope it will also make future cursor-handling changes (for instance for input method pre-editing) simpler. This commit makes the required semantic changes but doesn't make the rather more pervasive change of actually renaming the attributes from TATTR_ to ATTR_. That will be in the next commit.
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.