On Mon, Apr 29, 2024 at 08:18:00PM +0100, Mikhail Kot wrote:
> Hi!
>
> Sorry, didn't see your message.
> SGR allows you to specify color delimiters in two way: colon
> or semicolon. The semicolon version is now legacy one, and many
> applications, e.g. aerc (its library vaxis-ui, to be precise)
>
Hi,
On Mon, Apr 29, 2024 at 08:18:00PM +0100, Mikhail Kot wrote:
> Sorry, didn't see your message.
> SGR allows you to specify color delimiters in two way: colon
> or semicolon. The semicolon version is now legacy one, and many
> applications, e.g. aerc (its library vaxis-ui, to be precise)
> use
Hi!
Sorry, didn't see your message.
SGR allows you to specify color delimiters in two way: colon
or semicolon. The semicolon version is now legacy one, and many
applications, e.g. aerc (its library vaxis-ui, to be precise)
use colons by default. I believe it's better to support both
versions
--
Hi Mikhail,
> Colon-separated SGR (new version; ':' is the legacy one)
Could explain a bit more what this patch is about,
with some context and telling the goal?
Colon-separated SGR (new version; ':' is the legacy one)
---
st.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/st.c b/st.c
index b9f66e7..7c1cb9a 100644
--- a/st.c
+++ b/st.c
@@ -1149,7 +1149,7 @@ csiparse(void)
v = -1;
csiescseq.arg[c
Colon-separated SGR
---
st.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/st.c b/st.c
index b9f66e7..7c1cb9a 100644
--- a/st.c
+++ b/st.c
@@ -1149,7 +1149,7 @@ csiparse(void)
v = -1;
csiescseq.arg[csiescseq.narg++] = v;