Add missing st config
Use OpenBSD libraries in config.mk
Switch to using config.def.h
Apply blinking cursor patch
Switch from ^PgUp/Down to Shift+PgUp/Down
d4a62883 — Hiltjo Posthuma 1 year, 2 months ago
bump version to 0.8.4
3d13aef5 — Hiltjo Posthuma 1 year, 2 months ago
config.mk: use PKG_CONFIG in commented OpenBSD section
783af1bf — Hiltjo Posthuma 1 year, 2 months ago
LICENSE: bump years
288468ea — Hiltjo Posthuma 1 year, 2 months ago
remove sixel stub code

Remove stub code that was used for an experiment of adding sixel code to st
from the commit f7398434.
fe07b1a2 — Hiltjo Posthuma 1 year, 2 months ago
fix unicode glitch in DCS strings, patch by Tim Allen

Reported on the mailinglist:

I discovered recently that if an application running inside st tries to
send a DCS string, subsequent Unicode characters get messed up. For
example, consider the following test-case:

    printf '\303\277\033P\033\\\303\277'


  - \303\277 is the UTF-8 encoding of U+00FF LATIN SMALL LETTER Y WITH
    DIAERESIS (ÿ).
  - \033P is ESC P, the token that begins a DCS string.
  - \033\\ is ESC \, a token that ends a DCS string.
  - \303\277 is the same ÿ character again.

If I run the above command in a VTE-based terminal, or xterm, or
QTerminal, or pterm (PuTTY), I get the output:


...which is to say, the empty DCS string is ignored. However, if I run
that command inside st (as of commit 9ba7ecf), I get:


...where those last two characters are \303\277 interpreted as ISO8859-1
characters, instead of UTF-8.

I spent some time tracing through the state machines in st.c, and so far
as I can tell, this is how it works currently:

  - ESC P sets the "ESC_DCS" and "ESC_STR" flags, indicating that
    incoming bytes should be collected into the strescseq buffer, rather
    than being interpreted.
  - ESC \ sets the "ESC_STR_END" flag (when ESC is received), and then
    calls strhandle() (when \ is received) to interpret the collected
  - If the collected bytes begin with 'P' (i.e. if this was a DCS
    string) strhandle() sets the "ESC_DCS" flag again, confusing the
    state machine.

If my understanding is correct, fixing the problem should be as easy as
removing the line that sets ESC_DCS from strhandle():

diff --git a/st.c b/st.c
index ef8abd5..b5b805a 100644
--- a/st.c
+++ b/st.c
@@ -1897,7 +1897,6 @@ strhandle(void)
	case 'P': /* DCS -- Device Control String */
-		term.mode |= ESC_DCS;
	case '_': /* APC -- Application Program Command */
	case '^': /* PM -- Privacy Message */

I've tried the above patch and it fixes my problem, but I don't know if
it introduces any others.
d1ba9274 — Hiltjo Posthuma 1 year, 3 months ago
FAQ: fix single-buffer patch

rebase against master
c81f54af — Hiltjo Posthuma 1 year, 3 months ago
config.def.h: add an option allowwindowops, by default off (secure)

Similar to the xterm AllowWindowOps option, this is an option to allow or
disallow certain (non-interactive) operations that can be insecure or

NOTE: xsettitle() is not guarded by this because st does not support printing
the window title. Else this could be exploitable (arbitrary code execution).
Similar problems have been found in the past in other terminal emulators.

The sequence for base64-encoded clipboard copy is now guarded because it allows
a sequence written to the terminal to manipulate the clipboard of the running
user non-interactively, for example:

printf '\x1b]52;0;ZWNobyBoaQ0=\a'
3d047b2c — Hiltjo Posthuma 1 year, 3 months ago
FAQ: add some details about the w3m img hack

... and an example patch to switch from double-buffering to a single buffer.
002ccf35 — Hiltjo Posthuma 1 year, 3 months ago
tiny style fix
229597ad — Hiltjo Posthuma 1 year, 3 months ago
Partially add back in "support REP (repeat) escape sequence"

Add the functionality back in for xterm compatibility, but do not expose the
capability in st.info (yet).

Some notes:

It was reverted because it caused some issues with ncurses in some
configurations, namely when using BSD padding (--enable-bsdpad, BSD_TPUTS) in
ncurses it caused issues with repeating digits.

A fix has been upstreamed in ncurses since snapshot 20200523. The fix is also
backported to OpenBSD -current.
Call xsetcursor to set win.cursor in main

In xsetcursor, remove "DEFAULT(cursor, 1)" because 0 is a valid value.
Increase max allowed value of cursor from 6 to 7 (st extension).
8bd1a44f — Hiltjo Posthuma 1 year, 4 months ago
Revert "support REP (repeat) escape sequence"

This reverts commit e8392b282c2eaa28725241a9612804fb55113da4.

There is currently a bug in older ncurses versions (like on OpenBSD) where a
fix for a bug with REP is not backported yet. Most likely in tty/tty_update.c:

Noticed while using lynx (which uses ncurses/curses).
To reproduce using lynx: echo "Z0000000" | lynx -stdin

or using the program:

	WINDOW *win;
	win = initscr();




	return 0;

This prints "ZZZZZZZ" (incorrectly).
5ba924fd — Avi Halachmi (:avih) 1 year, 4 months ago
support REP (repeat) escape sequence

The sequence \e[Nb prints the last printed char N (more) times if it's
printable, and it's ignored after newline or other control chars.

This is Ecma-048/ANSI-X3.6 sequence and not DEC VT. It's supported by
xterm, and ncurses uses it when possible, e.g. when TERM is xterm* (and
with this commit also st*).

xterm supports only codepoints<=255, possibly due to internal limits.
We support any value/codepoint which was placed in a cell.

To test:
- tput rep 65 4 -> prints 'AAAA'
- printf "\342\225\246\033[4b" -> prints U+2566 1+4 times.
a404ac1c — Roberto E. Vargas 1 year, 4 months ago
Add rin terminfo capability

Tianlin Qu discovered that st is missing rin (scroll back #1 lines).