From: Johannes Altmanninger via pve-devel <pve-devel@lists.proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Johannes Altmanninger <aclopte@gmail.com>
Subject: [pve-devel] [PATCH vncterm v2 2/3] Parse more OSC sequences
Date: Thu, 25 Sep 2025 08:15:41 +0200 [thread overview]
Message-ID: <mailman.427.1758873888.390.pve-devel@lists.proxmox.com> (raw)
In-Reply-To: <20250925061600.11818-1-aclopte@gmail.com>
[-- Attachment #1: Type: message/rfc822, Size: 6334 bytes --]
From: Johannes Altmanninger <aclopte@gmail.com>
To: pve-devel@lists.proxmox.com
Cc: Johannes Altmanninger <aclopte@gmail.com>
Subject: [PATCH vncterm v2 2/3] Parse more OSC sequences
Date: Thu, 25 Sep 2025 08:15:41 +0200
Message-ID: <20250925061600.11818-2-aclopte@gmail.com>
To reproduce the problem, run in Bash:
$ printf '\x1b]133;A;click_events=1\x07'
Fixes https://bugzilla.proxmox.com/show_bug.cgi?id=6575
Signed-off-by: Johannes Altmanninger <aclopte@gmail.com>
---
vncterm.c | 11 +----------
1 file changed, 1 insertion(+), 10 deletions(-)
diff --git a/vncterm.c b/vncterm.c
index 71baa65..9830f21 100644
--- a/vncterm.c
+++ b/vncterm.c
@@ -1271,17 +1271,8 @@ static void vncterm_putchar(vncTerm *vt, unicode ch) {
case 'R': /* reset palette */
// fixme: reset_palette(vc);
break;
- case '0':
- case '1':
- case '2':
- case '4':
- vt->tty_state = ESosc;
- break;
default:
-#ifdef DEBUG
- fprintf(stderr, "unhandled OSC %c\n", ch);
-#endif
- vt->tty_state = ESnormal;
+ vt->tty_state = ESosc;
break;
}
break;
--
2.51.0.167.g6ad8021821.dirty
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-09-26 8:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250823083010.145866-1-aclopte@gmail.com>
2025-08-23 8:17 ` [pve-devel] [PATCH vncterm 1/4] Remove dead code and buffer-overflow Johannes Altmanninger via pve-devel
2025-08-23 8:17 ` [pve-devel] [PATCH vncterm 2/4] Remove unused state from OSC parser Johannes Altmanninger via pve-devel
2025-08-23 8:17 ` [pve-devel] [PATCH vncterm 3/4] Parse more OSC sequences Johannes Altmanninger via pve-devel
2025-08-23 8:17 ` [pve-devel] [PATCH vncterm 4/4] Also parse DCS commands Johannes Altmanninger via pve-devel
2025-09-25 6:15 ` [pve-devel] [PATCH vncterm v2 1/3] Remove unused state from OSC parser Johannes Altmanninger via pve-devel
[not found] ` <20250925061600.11818-1-aclopte@gmail.com>
2025-09-25 6:15 ` Johannes Altmanninger via pve-devel [this message]
2025-09-25 6:15 ` [pve-devel] [PATCH vncterm v2 3/3] Also parse DCS commands Johannes Altmanninger via pve-devel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mailman.427.1758873888.390.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=aclopte@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox