From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Tammo Block <tammo.block@gmail.com>
Cc: linux-kernel@vger.kernel.org, Jiri Slaby <jslaby@suse.com>,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH v3 0/6] vt: Add SRG mouse reporting features
Date: Mon, 5 Oct 2020 10:19:39 +0200 [thread overview]
Message-ID: <20201005081939.GA407265@kroah.com> (raw)
In-Reply-To: <CAEHKo2nK+S42FmjN3NDh8g8+yNvcpeBAbY8sq+wUxbRmZcbCGA@mail.gmail.com>
On Mon, Oct 05, 2020 at 10:06:38AM +0200, Tammo Block wrote:
> Hi Greg,
>
> Am Fr., 2. Okt. 2020 um 14:30 Uhr schrieb Greg Kroah-Hartman
> <gregkh@linuxfoundation.org>:
> >
> > On Mon, Jul 06, 2020 at 12:57:22PM +0200, Tammo Block wrote:
> > > Hi everybody,
> > >
> > > this patchset adds xterm like mouse reporting features to the console.
> > >
> > > The linux virtual console has support for mouse reporting since 1994 or so,
> > > but the kernel only supports the original X10/X11 style standard protocols.
> > > To support more protocols these patches expand the kernel structures in a
> > > up- and downwards compatible way, see the last patch for detailed
> > > documentation and pointers to even more detailed docs.
> > >
> > > The main goal is to become compatible with xterm, as most TUI software today
> > > is tested in xterm or another compatible terminal.
> > >
> > > Support by the mouse daemons (consolation, gpm) will be needed too.
> >
> > What happened to this feature. Was there a new set of patches or was
> > this the last one?
>
> This was the last set, there were no further comments in any direction.
>
> > mouse support for the console feels odd these dyas, who would use this?
> >
> Well .... at least i am using it .. ;-)
>
> This is in fact not a really new feature, but an improvement of an old feature.
> The patch just tries to be compatible with xterm and other modern terminals
> to be able to run stuff like midnight commander or similar programs.
>
> I am personally using console tty's for long running or controlling stuff
> and being able to use the mouse (especially for cut n' paste) seems useful.
> At least for me. But my personal habits might be odd ...
>
> Feel free to ignore the patches if you don't consider this feature useful.
> If you do consider it useful I can rebase against whatever you like.
Rebasing against 5.10-rc1 comes out in a few weeks, and resending it
then seems like a good idea.
thanks,
greg k-h
prev parent reply other threads:[~2020-10-05 8:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 10:57 [PATCH v3 0/6] vt: Add SRG mouse reporting features Tammo Block
2020-07-06 10:57 ` [PATCH v3 1/6] tiocl.h: Change/Add defines for mouse report Tammo Block
2020-07-06 10:58 ` [PATCH v3 2/6] console_struct.h: Add members " Tammo Block
2020-07-06 10:58 ` [PATCH v3 3/6] vt/vt: Enable mode change via escape sequence Tammo Block
2020-07-06 10:58 ` [PATCH v3 4/6] vt/vt: Add SRG mouse reporting protocol Tammo Block
2020-07-06 10:59 ` [PATCH v3 5/6] vt/vt: Add URXVT " Tammo Block
2020-07-06 11:00 ` [PATCH v3 6/6] Documentation: Describe console mouse reporting Tammo Block
2020-07-06 18:43 ` Randy Dunlap
2020-10-02 12:30 ` [PATCH v3 0/6] vt: Add SRG mouse reporting features Greg Kroah-Hartman
2020-10-05 8:06 ` Tammo Block
2020-10-05 8:19 ` Greg Kroah-Hartman [this message]
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=20201005081939.GA407265@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=tammo.block@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.