public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Pedro Alves <pedro@palves.net>, Hannes Domani <ssbssa@yahoo.de>,
	Hannes Domani via Gdb-patches <gdb-patches@sourceware.org>,
	Tom Tromey <tom@tromey.com>,
	Joel Brobecker <brobecker@adacore.com>
Subject: Re: [PATCHv3 1/2] Initial TUI mouse support
Date: Fri, 4 Jun 2021 14:13:58 -0400	[thread overview]
Message-ID: <45415d6f-45f8-c709-5a21-dd2b02e724f3@polymtl.ca> (raw)
In-Reply-To: <0936428e-80c4-c192-cdfd-817ff9bcfab0@palves.net>

On 2021-06-04 12:29 p.m., Pedro Alves wrote:
> The trouble is that now pressing anywhere on the screen with the mouse just results in
> weird characters being printed on the command line window (probably uninterpreted control
> sequences).  That even prevents me from selecting text (something I do often) -- I wanted to do
> that to paste the results here.  I even tried suspending GDB with ^Z to then copy the text, but
> that still leaves the mouse messed up.  See this screenshot:
> 
>   https://i.imgur.com/bO7FKDO.png
> 
> This was on Ubuntu 20.04.

Obviously the printing random characters is bad.  But it's possible that
the not being able to select text is normal, as the application (GDB)
now supports mouse events.  In some terminal emulators, you can press
shift while you click to say "I really want to select the display
characters, not send mouse events to the program".

It's the same with other TUI apps for me:

 - tmux (with "set -g mouse on" in ~/.tmux.conf)
 - tig (I don't remember if anything is needed to enable mouse support)
 - weechat (I don't remember if anything is needed to enable mouse
   support)

In some of these programs, mouse support is disabled by default and you
have to use some setting to enable it.  So by default, standard
selection would work.  But if you enable mouse suport, then you have to
use shift+click to select.

Simon

  parent reply	other threads:[~2021-06-04 18:14 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210603151453.15248-1-ssbssa.ref@yahoo.de>
2021-06-03 15:14 ` Hannes Domani
2021-06-03 15:14   ` [PATCHv3 2/2] Forward mouse click to python TUI window Hannes Domani
2021-06-03 17:16     ` Eli Zaretskii
2021-06-04 13:52     ` Tom Tromey
2021-06-04 13:51   ` [PATCHv3 1/2] Initial TUI mouse support Tom Tromey
2021-06-04 14:21     ` Hannes Domani
2021-06-04 15:20       ` Pedro Alves
2021-06-04 16:06         ` Hannes Domani
2021-06-04 16:23           ` Pedro Alves
2021-06-04 18:59             ` Eli Zaretskii
2021-06-04 18:57           ` Eli Zaretskii
2021-06-04 16:29         ` Pedro Alves
2021-06-04 16:48           ` Hannes Domani
2021-06-04 18:05             ` Joel Brobecker
2021-06-04 18:13           ` Simon Marchi [this message]
2021-06-04 18:39             ` Joel Brobecker
2021-06-04 20:31             ` Pedro Alves
2021-06-04 20:43               ` Pedro Alves
2021-06-04 21:15               ` Hannes Domani
2021-06-04 22:19                 ` Pedro Alves
2021-06-10 18:44               ` Tom Tromey
2021-06-13 17:26                 ` Pedro Alves
2021-06-18 15:01                   ` Tom Tromey
2021-06-18 17:42                     ` Pedro Alves
2021-06-04 18:46           ` Tom Tromey
2021-06-04 20:54             ` Pedro Alves
2021-06-04 23:48               ` Pedro Alves
2021-06-05 14:40                 ` Hannes Domani
2021-06-06  5:46                   ` Eli Zaretskii
2021-06-10 18:46                   ` Tom Tromey
2021-06-11 11:02                     ` Hannes Domani
2021-06-12  2:41                       ` POC: Make the TUI command window support the mouse (Re: [PATCHv3 1/2] Initial TUI mouse support) Pedro Alves
2021-06-12 12:32                         ` Hannes Domani
2021-06-12 18:08                           ` Pedro Alves
2021-06-13  2:46                             ` [PATCH v2] Make the TUI command window support the mouse Pedro Alves
2021-06-13 10:35                               ` Eli Zaretskii
2021-06-13 17:29                                 ` Pedro Alves
2021-06-13 18:02                                   ` Eli Zaretskii
2021-06-13 18:13                                     ` Pedro Alves
2021-06-13 13:04                               ` Hannes Domani
2021-06-13 17:25                                 ` [PATCH v3] " Pedro Alves
2021-06-13 17:55                                   ` Hannes Domani
2021-06-13 17:59                                     ` Pedro Alves
2021-06-17 11:04                                       ` [PUSHED v4] " Pedro Alves

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=45415d6f-45f8-c709-5a21-dd2b02e724f3@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@palves.net \
    --cc=ssbssa@yahoo.de \
    --cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).