Package Details: st 0.8.4-1

Git Clone URL: (read-only, click to copy)
Package Base: st
Description: A simple virtual terminal emulator for X.
Upstream URL:
Licenses: MIT
Submitter: Foxboron
Maintainer: jose1711 (waschtl)
Last Packager: jose1711
Votes: 64
Popularity: 2.72
First Submitted: 2017-11-20 15:32
Last Updated: 2020-06-19 21:19

Latest Comments

1 2 3 4 Next › Last »

ilf0 commented on 2020-06-20 12:39

Are README.terminfo.rst and terminfo.patch still needed with 0.8.4? README.terminfo.rst sais " As of st-0.8.2 they have errors in them. This has been fixed and will roll out in the next release, though."

E5ten commented on 2020-06-02 16:37

Can you change the installopts to be '-m 0644 -D -t' so that install implementations aside from coreutils work, because those shortopt equivalents to the long options currently used are more widely supported, whereas the long options are pretty much only supported by GNU coreutils.

kolo commented on 2020-04-17 22:03

Attempting to add the font2 patch creates error: "error: ‘frccap’ undeclared". Some reddit threads suggest this has been a problem for over 9 months now. The following relevant patches from the official st repos will fix this:

2019-03-03 10:29 simplify (greedy) font caching allocating a bit Hiltjo Posthuma 1 +2 -7

2019-02-28 01:56 fix use after free in font caching algorithm magras 1 +9 -6

milouse commented on 2020-01-27 08:34

AUR helpers are not supported. Please contact pikaur author to get help with it. st works like any other aur package: after having cloned it, you can makepkg it and you'll find the sources in the src folder.

etognoni commented on 2020-01-26 17:42

First time , for me, after install i cant find sources, is that normal? using pikaur i cant find build folder.

Tetrapyle commented on 2019-11-11 18:07

Ooups, I suppose I messed with something :)

waschtl commented on 2019-11-11 14:37

It looks like you have your own config.h. The error message is pointing at line 180 in that file.

If you didn't intend to compile with customizations, just remove your config.h, and the defaults from config.def.h will be used. If you did intend to compile with customizations, you probably need to adjust your config.h.

Tetrapyle commented on 2019-11-11 09:24

Hi, It doesn't compile on my system:

$ LC_MESSAGES=en_US.UTF-8 makepkg -si
==> Making package: st 0.8.2-10 (lun. 11 nov. 2019 10:16:42 CET)


==> Starting build()...


st build options:
CFLAGS  = -I/usr/include/X11  -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include   -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include  -DVERSION="0.8.2" -D_XOPEN_SOURCE=600 -D_FORTIFY_SOURCE=2 -march=x86-64 -mtune=generic -O2 -pipe -fno-plt
LDFLAGS = -L/usr/lib/X11 -lm -lrt -lX11 -lutil -lXft  -lfontconfig -lfreetype   -lfreetype  -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now
CC      = c99
c99 -I/usr/include/X11  `pkg-config --cflags fontconfig`  `pkg-config --cflags freetype2` -DVERSION=\"0.8.2\" -D_XOPEN_SOURCE=600 -D_FORTIFY_SOURCE=2 -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -c st.c
lkc99 -I/usr/include/X11  `pkg-config --cflags fontconfig`  `pkg-config --cflags freetype2` -DVERSION=\"0.8.2\" -D_XOPEN_SOURCE=600 -D_FORTIFY_SOURCE=2 -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -c x.c
In file included from x.c:61:
config.h:180:42: error: ‘iso14755’ undeclared here (not in a function)
  180 |  { TERMMOD,              XK_I,           iso14755,       {.i =  0} },
      |                                          ^~~~~~~~
make: *** [Makefile:22: x.o] Error 1
make: Leaving directory '/home/jean/abs/st/src/st-0.8.2'
==> ERROR: A failure occurred in build().

waschtl commented on 2019-11-03 19:54

Hi @milouse,

my conversation so far with Thomas Dickey from ncurses ( has revealed something that I didn't previously realize:

  • The terminfo entries from upstream st have two bad tmux extensions in them. While they don't cause any obvious errors while I'm using them, that may not be the case in general. I don't think that they should be distributed.
  • He regularly releases an updated terminfo database between ncurses versions that is intended to be included in distribution packages. ArchLinux is not doing this.
  • He believes his current st terminfo entry to be correct. I have not verified this yet.
  • There is a clear argument for distributing all terminfo entries with ncurses: When you ssh into a machine, that machine must know your terminal emulator. Most terminal emulators don't get installed on most machines (especially servers).

I have analyzed various terminfo entries for st from several ncurses versions, as well as from upstream st. I now understand what's wrong with the entries provided with st and am working on understanding his modifications to it.

My plan is as follows:

  1. Clear up any questions I have about the current st terminfo file provided by ncurses.
  2. Test entries that should be good.
  3. File a bug report and patch with st to fix the problems with their terminfo entry.
  4. File a bug report with the ArchLinux ncurses package hoping to move them to use officially released and updated terminfo databases between ncurses versions.

Thanks for your encouragement.

milouse commented on 2019-11-01 10:18

Hi @waschtl,

I just read with attention your README about the terminfo problem. I'm aware of it since a long time, but must admit I never take time to do anything forward. Thus I'm very insteresting to follow up your discussion with either ncurse team or Archlinux team. How do you think to proceed? A quick check in the archlinux bug tracker show me no bug related to that. I wonder if a quick fix won't be to ask there to remove st information from the archlinux ncurse package. As st is NOT provided in any official repository, I think it's not a big problem to remove responsibility of that.

Thank you for your involvment!