Package Details: st 0.8.5-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: 73
Popularity: 0.68
First Submitted: 2017-11-20 15:32
Last Updated: 2022-01-07 17:29

Dependencies (1)

Required by (4)

Sources (3)

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

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!

simona commented on 2019-10-31 10:11

Yes :-) Thanks.

waschtl commented on 2019-10-31 00:24

No problem. I think I will remove the error message. It's counterintuitive.

I did not know about BlackArch. Thanks for the pointer.

simona commented on 2019-10-31 00:03

  1. yes, sorry. blackarch repos.

waschtl commented on 2019-10-31 00:00

@simona, two questions:

  1. Where is yay finding the package paraxor-st? I can't find it in the AUR.

    yay -Si paraxor-st

  2. Does installing st work if you try again?

    The error message you are reporting is there so that you know that st can only be configured before compilation. If yay caches the package directory, a second attempt should no longer show the error.

simona commented on 2019-10-30 23:49

Yes. yay was installing paraxor-st. another pkg. But installing true st it give me:

patching file Makefile ==> ERRORE: This package can be configured in config.h. Copy config.def.h just placed into the package directory to config.h and modify it to change the configuration. Or just leave it alone to use default values. Then restart the build process. ==> ERRORE: Si è verificato un errore in prepare(). L'operazione sta per essere interrotta...

waschtl commented on 2019-10-30 23:46

@simona, you should be fine as it is. I may have expressed myself poorly. I meant to say that the package does not put any files in /usr/share/terminfo.

Are you getting an error message?

simona commented on 2019-10-30 23:22

@waschtl can I change where to install? I use yay.