diff options
author | Kai Hendry <hendry@webconverger.com> | 2013-04-09 22:13:54 +0100 |
---|---|---|
committer | Christoph Lohmann <20h@r-36.net> | 2013-04-13 08:25:07 +0200 |
commit | ddd429ea2478beeb7d17d9b548abd9173049dcc6 (patch) | |
tree | c1562d20040661787c449e8850218f52871cc7c1 /FAQ | |
parent | 684cf55a0d21da19a6e9e4a490a7c4dd3334638d (diff) | |
download | st-patched-ddd429ea2478beeb7d17d9b548abd9173049dcc6.tar.bz2 st-patched-ddd429ea2478beeb7d17d9b548abd9173049dcc6.tar.xz st-patched-ddd429ea2478beeb7d17d9b548abd9173049dcc6.zip |
Convert FAQ into Markdown, to make it easier to integrate it into http://st.suckless.org/
Signed-off-by: Christoph Lohmann <20h@r-36.net>
Diffstat (limited to 'FAQ')
-rw-r--r-- | FAQ | 62 |
1 files changed, 26 insertions, 36 deletions
@@ -1,43 +1,35 @@ | |||
1 | -- | 1 | ## Why does st not handle utmp entries? |
2 | Why does st not handle utmp entries? | ||
3 | 2 | ||
4 | Use the excellent tool of utmp[0] for this task. | 3 | Use the excellent tool of [utmp](http://git.suckless.org/utmp/) for this task. |
5 | 4 | ||
6 | [0] http://git.suckless.org/utmp/ | 5 | ## Some _random program_ complains that st is unknown/not recognised/unsupported/whatever! |
7 | -- | ||
8 | Some _random program_ complains that st is unknown/not | ||
9 | recognised/unsupported/whatever! | ||
10 | 6 | ||
11 | It means that st doesn’t have any terminfo entry on your system. Chances are | 7 | It means that st doesn’t have any terminfo entry on your system. Chances are |
12 | you did not make install. If you just want to test it without installing it, | 8 | you did not `make install`. If you just want to test it without installing it, |
13 | you can manualy run tic -s st.info in st dir. It will compile st.info into a | 9 | you can manualy run `tic -s st.info`. |
14 | fully working local terminfo description. You can delete it when you’re done. | 10 | |
15 | -- | 11 | ## Nothing works, and nothing is said about an unknown terminal! |
16 | Nothing works, and nothing is said about an unknown terminal! | ||
17 | 12 | ||
18 | * Some programs just assume they’re running in xterm i.e. they don’t rely on | 13 | * Some programs just assume they’re running in xterm i.e. they don’t rely on |
19 | terminfo. What you see is the current state of the “xterm compliance”. | 14 | terminfo. What you see is the current state of the “xterm compliance”. |
20 | * Some programs don’t complain about the lacking st description and default to | 15 | * Some programs don’t complain about the lacking st description and default to |
21 | another terminal. In that case see the question about terminfo. | 16 | another terminal. In that case see the question about terminfo. |
22 | -- | 17 | |
23 | I get some weird glitches/visual bug on _random program_! | 18 | ## I get some weird glitches/visual bug on _random program_! |
24 | 19 | ||
25 | Try lauching it with a different TERM: $ TERM=xterm myapp. toe(1) will give | 20 | Try launching it with a different TERM: $ TERM=xterm myapp. toe(1) will give |
26 | you a list of available terminals, but you’ll most likely switch between | 21 | you a list of available terminals, but you’ll most likely switch between xterm, |
27 | xterm, st or st-256color. The default value for TERM can be changed in | 22 | st or st-256color. The default value for TERM can be changed in config.h |
28 | config.h (TNAME). | 23 | (TNAME). |
29 | -- | 24 | |
30 | How do I scroll back up? | 25 | ## How do I scroll back up? |
31 | 26 | ||
32 | Invoke st with a screen multiplexer like GNU screen[0] or tmux[1]. | 27 | Using a terminal multiplexer. |
33 | st -e screen works better for text reflowing. To enter screen’s scroll | 28 | |
34 | back mode aka “copy mode”, it’s C-a ESC. You probably want defscrollback | 29 | * `st -e tmux` using C-a [ |
35 | 10000 in your ~/.screenrc too. | 30 | * `st -e screen` using C-a ESC |
36 | 31 | ||
37 | [0] http://en.wikipedia.org/wiki/GNU_Screen | 32 | ## Why doesn't the Del key work in some programs? |
38 | [1] http://en.wikipedia.org/wiki/Tmux | ||
39 | -- | ||
40 | Why doesn't the Del key work in some programs? | ||
41 | 33 | ||
42 | Taken from the terminfo manpage: | 34 | Taken from the terminfo manpage: |
43 | 35 | ||
@@ -49,14 +41,14 @@ Taken from the terminfo manpage: | |||
49 | codes as smkx and rmkx. Otherwise the keypad is assumed to | 41 | codes as smkx and rmkx. Otherwise the keypad is assumed to |
50 | always transmit. | 42 | always transmit. |
51 | 43 | ||
52 | In the st case smkx=\E[?1h\E= and rmkx=\E[?1l\E>, so it is mandatory that | 44 | In the st case smkx=E[?1hE= and rmkx=E[?1lE>, so it is mandatory that |
53 | applications which want to test against keypad keys, have to send these | 45 | applications which want to test against keypad keys, have to send these |
54 | sequences. | 46 | sequences. |
55 | 47 | ||
56 | But buggy applications like bash and irssi for example don't do this. A fast | 48 | But buggy applications like bash and irssi for example don't do this. A fast |
57 | solution for them is to use the following command: | 49 | solution for them is to use the following command: |
58 | 50 | ||
59 | $ printf "\033?1h\033=" >/dev/tty | 51 | $ printf "�33?1h�33=" >/dev/tty |
60 | 52 | ||
61 | or | 53 | or |
62 | $ echo $(tput smkx) >/dev/tty | 54 | $ echo $(tput smkx) >/dev/tty |
@@ -73,7 +65,7 @@ Adding this option to your .inputrc will fix the keypad problem for all | |||
73 | applications using readline. | 65 | applications using readline. |
74 | 66 | ||
75 | If you are using zsh, then read the zsh FAQ | 67 | If you are using zsh, then read the zsh FAQ |
76 | (http://zsh.sourceforge.net/FAQ/zshfaq03.html#l25): | 68 | <http://zsh.sourceforge.net/FAQ/zshfaq03.html#l25>: |
77 | 69 | ||
78 | It should be noted that the O / [ confusion can occur with other keys | 70 | It should be noted that the O / [ confusion can occur with other keys |
79 | such as Home and End. Some systems let you query the key sequences | 71 | such as Home and End. Some systems let you query the key sequences |
@@ -91,5 +83,3 @@ If you are using zsh, then read the zsh FAQ | |||
91 | zle -N zle-line-finish | 83 | zle -N zle-line-finish |
92 | 84 | ||
93 | Putting these lines into your .zshrc will fix the problems. | 85 | Putting these lines into your .zshrc will fix the problems. |
94 | -- | ||
95 | |||