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 0/4 vncterm] Fix OSC parser
Date: Sat, 23 Aug 2025 10:17:04 +0200 [thread overview]
Message-ID: <mailman.466.1756280114.385.pve-devel@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 6114 bytes --]
From: Johannes Altmanninger <aclopte@gmail.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH 0/4 vncterm] Fix OSC parser
Date: Sat, 23 Aug 2025 10:17:04 +0200
Message-ID: <20250823083010.145866-1-aclopte@gmail.com>
This is my attempt to fix https://bugzilla.proxmox.com/show_bug.cgi?id=6575
(reported elsewhere as
https://github.com/fish-shell/fish-shell/issues/11609#issuecomment-3114092441
https://github.com/fish-shell/fish-shell/issues/11749)
Untested since I'm not sure how to compile this -- it seems to require a Debian
system since "make" fails with "Makefile:1: /usr/share/dpkg/pkg-info.mk:
No such file or directory" here. I have also never used Proxmox, so I'd
prefer someone else to take this over the finish line.
At least spiceterm has the same issues. I don't think the code duplication
makes sense, maybe extract a library?
Until then, I suppose I can send the same series for spiceterm
if no one else does.
vncterm.c | 42 +++++++-----------------------------------
vncterm.h | 2 --
2 files changed, 7 insertions(+), 37 deletions(-)
[-- 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
reply other threads:[~2025-08-27 7:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.466.1756280114.385.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.