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.

85 lines
3.2 KiB

  1. ## Why does st not handle utmp entries?
  2. Use the excellent tool of [utmp](http://git.suckless.org/utmp/) for this task.
  3. ## Some _random program_ complains that st is unknown/not recognised/unsupported/whatever!
  4. It means that st doesn’t have any terminfo entry on your system. Chances are
  5. you did not `make install`. If you just want to test it without installing it,
  6. you can manualy run `tic -s st.info`.
  7. ## Nothing works, and nothing is said about an unknown terminal!
  8. * Some programs just assume they’re running in xterm i.e. they don’t rely on
  9. terminfo. What you see is the current state of the “xterm compliance”.
  10. * Some programs don’t complain about the lacking st description and default to
  11. another terminal. In that case see the question about terminfo.
  12. ## I get some weird glitches/visual bug on _random program_!
  13. Try launching it with a different TERM: $ TERM=xterm myapp. toe(1) will give
  14. you a list of available terminals, but you’ll most likely switch between xterm,
  15. st or st-256color. The default value for TERM can be changed in config.h
  16. (TNAME).
  17. ## How do I scroll back up?
  18. Using a terminal multiplexer.
  19. * `st -e tmux` using C-a [
  20. * `st -e screen` using C-a ESC
  21. ## Why doesn't the Del key work in some programs?
  22. Taken from the terminfo manpage:
  23. If the terminal has a keypad that transmits codes when the keys
  24. are pressed, this information can be given. Note that it is not
  25. possible to handle terminals where the keypad only works in
  26. local (this applies, for example, to the unshifted HP 2621 keys).
  27. If the keypad can be set to transmit or not transmit, tive these
  28. codes as smkx and rmkx. Otherwise the keypad is assumed to
  29. always transmit.
  30. In the st case smkx=E[?1hE= and rmkx=E[?1lE>, so it is mandatory that
  31. applications which want to test against keypad keys, have to send these
  32. sequences.
  33. But buggy applications like bash and irssi for example don't do this. A fast
  34. solution for them is to use the following command:
  35. $ printf "\033?1h\033=" >/dev/tty
  36. or
  37. $ echo $(tput smkx) >/dev/tty
  38. In the case of bash readline is used. Readline has a different note in its
  39. manpage about this issue:
  40. enable-keypad (Off)
  41. When set to On, readline will try to enable the
  42. application keypad when it is called. Some systems
  43. need this to enable arrow keys.
  44. Adding this option to your .inputrc will fix the keypad problem for all
  45. applications using readline.
  46. If you are using zsh, then read the zsh FAQ
  47. <http://zsh.sourceforge.net/FAQ/zshfaq03.html#l25>:
  48. It should be noted that the O / [ confusion can occur with other keys
  49. such as Home and End. Some systems let you query the key sequences
  50. sent by these keys from the system's terminal database, terminfo.
  51. Unfortunately, the key sequences given there typically apply to the
  52. mode that is not the one zsh uses by default (it's the "application"
  53. mode rather than the "raw" mode). Explaining the use of terminfo is
  54. outside of the scope of this FAQ, but if you wish to use the key
  55. sequences given there you can tell the line editor to turn on
  56. "application" mode when it starts and turn it off when it stops:
  57. function zle-line-init () { echoti smkx }
  58. function zle-line-finish () { echoti rmkx }
  59. zle -N zle-line-init
  60. zle -N zle-line-finish
  61. Putting these lines into your .zshrc will fix the problems.