From: Pedro Alves <pedro@palves.net>
To: strager <strager.nds@gmail.com>,
Andrew Burgess <aburgess@redhat.com>,
Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/tui: add 'set tui mouse-events off' to restore mouse selection
Date: Thu, 2 Feb 2023 19:50:34 +0000 [thread overview]
Message-ID: <f494b233-31bd-4278-a55f-8f3234d40eb7@palves.net> (raw)
In-Reply-To: <CAC-ggsHb6P2hS9FsVfan6ZEk9JSU=Zqt1PKvkfLSn33iRcF-6A@mail.gmail.com>
On 2023-02-02 1:08 a.m., strager via Gdb-patches wrote:
> --- gdb/doc/gdb.texinfo
> +++ gdb/doc/gdb.texinfo
> @@ -29606,7 +29606,13 @@ the @key{SHIFT} key on your keyboard to
> temporarily bypass
> @value{GDBN}'s TUI and access the terminal's native mouse copy/paste
> functionality (commonly, click-drag-release or double-click to select
> text, middle-click to paste). This copy/paste works with the
> -terminal's selection buffer, as opposed to the TUI's buffer.
> +terminal's selection buffer, as opposed to the TUI's buffer. Alternatively, to
> +disable mouse support in the TUI entirely and give the terminal control over
> +mouse clicks, turn off the @code{tui mouse-events} setting
> +(@pxref{tui-mouse-events,,set tui mouse-events}).
> +
I noticed the new command doesn't have a "set" callback, so I guess this means
that you have to disable and re-enable the TUI for the setting to take effect?
Or does it take effect immediately somehow?
next prev parent reply other threads:[~2023-02-02 19:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-28 0:42 strager
2023-01-28 8:35 ` Eli Zaretskii
2023-02-01 8:35 ` strager
2023-02-01 12:41 ` Eli Zaretskii
2023-02-01 13:27 ` Andrew Burgess
2023-02-02 1:08 ` strager
2023-02-02 7:18 ` Eli Zaretskii
2023-02-02 19:50 ` Pedro Alves [this message]
2023-02-02 19:59 ` strager
2023-09-14 8:05 ` strager
2023-09-20 15:39 ` Pedro Alves
2023-02-02 9:33 ` Lancelot SIX
2023-02-02 11:11 ` strager
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=f494b233-31bd-4278-a55f-8f3234d40eb7@palves.net \
--to=pedro@palves.net \
--cc=aburgess@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=strager.nds@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).