My build of suckless st terminal
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

75 lines
2.7 KiB

  1. --
  2. Why does st not handle utmp entries?
  3. Use the excellent tool of utmp[0] for this task.
  4. [0] http://git.suckless.org/utmp/
  5. --
  6. Some _random program_ complains that st is unknown/not
  7. recognised/unsupported/whatever!
  8. It means that st doesn’t have any terminfo entry on your system. Chances are
  9. you did not make install. If you just want to test it without installing it,
  10. you can manualy run tic -s st.info in st dir. It will compile st.info into a
  11. fully working local terminfo description. You can delete it when you’re done.
  12. --
  13. Nothing works, and nothing is said about an unknown terminal!
  14. * Some programs just assume they’re running in xterm i.e. they don’t rely on
  15. terminfo. What you see is the current state of the “xterm compliance”.
  16. * Some programs don’t complain about the lacking st description and default to
  17. another terminal. In that case see the question about terminfo.
  18. --
  19. I get some weird glitches/visual bug on _random program_!
  20. Try lauching it with a different TERM: $ TERM=xterm myapp. toe(1) will give
  21. you a list of available terminals, but you’ll most likely switch between
  22. xterm, st or st-256color. The default value for TERM can be changed in
  23. config.h (TNAME).
  24. --
  25. How do I scroll back up?
  26. Invoke st with a screen multiplexer like GNU screen[0] or tmux[1].
  27. st -e screen works better for text reflowing. To enter screen’s scroll
  28. back mode aka “copy mode”, it’s C-a ESC. You probably want defscrollback
  29. 10000 in your ~/.screenrc too.
  30. [0] http://en.wikipedia.org/wiki/GNU_Screen
  31. [1] http://en.wikipedia.org/wiki/Tmux
  32. --
  33. Why doesn't the Del key work in some programs?
  34. Taken from the terminfo manpage:
  35. If the terminal has a keypad that transmits codes when the keys
  36. are pressed, this information can be given. Note that it is not
  37. possible to handle terminals where the keypad only works in
  38. local (this applies, for example, to the unshifted HP 2621 keys).
  39. If the keypad can be set to transmit or not transmit, tive these
  40. codes as smkx and rmkx. Otherwise the keypad is assumed to
  41. always transmit.
  42. In the st case smkx=\E[?1h\E= and rmkx=\E[?1l\E>, so it is mandatory that
  43. applications which want to test against keypad keys, have to send these
  44. sequences.
  45. But buggy applications like bash and irssi for example don't do this. A fast
  46. solution for them is to use the following command:
  47. $ echo ^[?1h^[= >/dev/tty
  48. or
  49. $ echo $(tput smkx) >/dev/tty
  50. In the case of bash it is using readline, which has a different not in its
  51. manpage:
  52. enable-keypad (Off)
  53. When set to On, readline will try to enable the
  54. application keypad when it is called. Some systems
  55. need this to enable arrow keys.
  56. Adding this option to your .inputrc will fix the keypad problem for all
  57. applications using readline.
  58. --