All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tammo Block <tammo.block@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jslaby@suse.com>
Subject: [PATCH v2 5/6] vt/vt: Add URXVT mouse reporting protocol
Date: Wed, 1 Jul 2020 17:13:47 +0200	[thread overview]
Message-ID: <149cd3c8dcb13405af00a54248c6e218cc588c0d.1593615440.git.tammo.block@gmail.com> (raw)
In-Reply-To: <cover.1593615440.git.tammo.block@gmail.com>

The URXVT protocol easy, all data analog to the old X10.

Signed-off-by: Tammo Block <tammo.block@gmail.com>
---
 drivers/tty/vt/vt.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/drivers/tty/vt/vt.c b/drivers/tty/vt/vt.c
index 9aae3eac7989..33e43cbfa1fc 100644
--- a/drivers/tty/vt/vt.c
+++ b/drivers/tty/vt/vt.c
@@ -1861,6 +1861,9 @@ void mouse_report(struct tty_struct *tty, int butt, int mrx, int mry)
 			len = sprintf(buf, "\033[<%d;%d;%d%c", butt,
 					mrx + 1, mry + 1, rel ? 'm' : 'M');
 			break;
+		case Mouse_URXVT:
+			len = sprintf(buf, "\033[%d;%d;%dM", butt + 32, mrx + 1, mry + 1);
+			break;
 		default:
 			len = sprintf(buf, "\033[M%c%c%c", (char)(' ' + butt),
 					(char)('!' + mrx), (char)('!' + mry));
-- 
2.27.0


  parent reply	other threads:[~2020-07-01 15:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-01 15:11 [PATCH v2 0/6] vt: Add SRG mouse reporting features Tammo Block
2020-07-01 15:12 ` [PATCH v2 1/6] tiocl.h: Change/Add defines for mouse report Tammo Block
2020-07-01 15:12 ` [PATCH v2 2/6] console_struct.h: Two members " Tammo Block
2020-07-01 15:12 ` [PATCH v2 3/6] vt/vt: Enable mode change via escape sequence Tammo Block
2020-07-01 15:13 ` [PATCH v2 4/6] vt/vt: Add SRG mouse reporting protocol Tammo Block
2020-07-02  8:48   ` Jiri Slaby
2020-07-02 12:31     ` Tammo Block
2020-07-01 15:13 ` Tammo Block [this message]
2020-07-01 15:14 ` [PATCH v2 6/6] Documentation: Describe console mouse reporting Tammo Block
2020-07-01 15:31   ` Randy Dunlap

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=149cd3c8dcb13405af00a54248c6e218cc588c0d.1593615440.git.tammo.block@gmail.com \
    --to=tammo.block@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    /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.