st.git, branch mastermy rice of st
https://git.gustafrydholm.xyz/st.git/atom?h=master2023-07-11T12:06:12ZUpdate font style for nerd symbols2023-07-11T12:06:12ZGustaf Rydholmgustaf.rydholm@gmail.com2023-07-11T12:06:12Zurn:sha1:8c0bee8ab328825552874a78fc1d23da04060320ignore C1 control characters in UTF-8 mode2023-05-07T22:49:25ZHiltjo Posthumahiltjo@codemadness.org2023-02-07T19:00:59Zurn:sha1:3e1afae00450cf3ddadec904e3f37966bb866209
Ignore processing and printing C1 control characters in UTF-8 mode.
These are in the range: 0x80 - 0x9f.
By default in st the mode is set to UTF-8.
This matches more the behaviour of xterm with the options -u8 or +u8 also.
Also see the xterm resource "allowC1Printable".
Let me know if this breaks something, in most cases I don't think so.
As usual a very good reference is:
https://invisible-island.net/xterm/ctlseqs/ctlseqs.html
Add support for DSR response "OK" escape sequence2023-05-07T22:49:12ZAdam Pricekomidore64@gmail.com2023-02-07T18:54:29Zurn:sha1:9b61c72d8d171ddb1dec59f4cbf728766d2cfc40
"VT100 defines an escape sequence [1] called Device Status Report (DSR). When
the DSR sequence received is `csi 5n`, an "OK" response `csi 0n` is returned.
This patch adds that "OK" response.
I encountered this missing sequence when I noticed that fzf [2] would clobber
my prompt whenever completing a find.
To test that ST doesn't currently respond to `csi 5n`, use fzf's shell
extension in ST's repo to complete the path for a file.
my-fancy-prompt $ vim **<tab>
<select a file>
st.c
Select a file with <enter>, and notice that fzf clobbers some or all of your
prompt.
After applying this patch, do the same test as above and notice that fzf has no
longer clobbered your prompt by placing the file name in the correct position
in your command.
my-fancy-prompt $ vim **<tab>
<select a file>
my-fancy prompt $ vim st.c
Thank you for considering my first patch submission.
[1] https://www.xfree86.org/current/ctlseqs.html#VT100%20Mode
[2] https://github.com/junegunn/fzf
"
Patch slightly adapted with input from the mailinglist,
Fixed OSC color reset without parameter->resets all colors2023-05-07T22:48:54ZHiltjo Posthumahiltjo@codemadness.org2023-02-05T12:29:35Zurn:sha1:fd53c918d2e070b96a83c347ffefcf6842c3124f
Adapted from (garbled) patch by wim <wim@thinkerwim.org>
Additional notes: it should reset all the colors using xloadcols().
To reproduce: set a different (theme) color using some escape code, then reset
it:
printf '\x1b]104\x07'
fix buffer overflow when handling long composed input2023-05-07T22:48:42ZHiltjo Posthumahiltjo@codemadness.org2022-10-25T15:11:11Zurn:sha1:694803663e99299519e1dee88106adfc973c39b3
To reproduce the issue:
"
If you already have the multi-key enabled on your system, then add this line
to your ~/.XCompose file:
[...]
<question> <T> <E> <S> <T> <question> :
"1234567890123456789012345678901234567890123456789012345678901234567890"
"
Reported by and an initial patch by Andy Gozas <andy@gozas.me>, thanks!
Adapted the patch, for now st (like dmenu) handles a fixed amount of composed
characters, or otherwise ignores it. This is done for simplicity sake.
bump version to 0.92023-05-07T22:48:29ZHiltjo Posthumahiltjo@codemadness.org2022-10-04T17:40:30Zurn:sha1:e95ea6bb8fd0638d7e9d0f70a3cbfbed18264435FAQ: document the color emojis crash issue which affected some systems is fixed2023-05-07T22:48:15ZHiltjo Posthumahiltjo@codemadness.org2022-09-16T21:07:09Zurn:sha1:43fe8ada58d53585c3b1d283203a7ed577497ba2
It is fixed in libXft 2.3.6:
https://gitlab.freedesktop.org/xorg/lib/libxft/-/blob/libXft-2.3.5/NEWS
st: use `void' to indicate an empty parameter list2023-05-07T22:48:00ZTom Schwindlschwindl@posteo.de2022-08-18T14:55:19Zurn:sha1:05fb7587ede0790489e5a912182e0c79bc338708Makefile: add manual path for OpenBSD2023-05-07T22:47:46ZHiltjo Posthumahiltjo@codemadness.org2022-05-01T16:38:40Zurn:sha1:b40e01e0550e6e796c74a49583e1bbbf479d0199Merge 8629d9a1da72cc18568a8f146307b0e939b77ebf2023-05-07T22:47:23ZNRKnrk@disroot.org2022-01-07T17:21:04Zurn:sha1:cbe9567b1f59ef9c18412426a4b0a50ba2145b56