public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Hannes Domani <ssbssa@yahoo.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 3/3] Add setting to enable/disable TUI mouse handling
Date: Mon, 07 Jun 2021 19:49:16 +0300	[thread overview]
Message-ID: <83mts1fwmr.fsf@gnu.org> (raw)
In-Reply-To: <20210607163003.621-3-ssbssa@yahoo.de> (message from Hannes Domani via Gdb-patches on Mon, 7 Jun 2021 18:30:03 +0200)

> Date: Mon,  7 Jun 2021 18:30:03 +0200
> From: Hannes Domani via Gdb-patches <gdb-patches@sourceware.org>
> 
> Useful if the mouse events don't work correctly on a system, or the user just
> doesn't need them.
> 
> gdb/ChangeLog:
> 
> 2021-06-07  Hannes Domani  <ssbssa@yahoo.de>
> 
> 	* tui/tui-data.c (tui_set_win_focus_to): Handle mouse setting.
> 	* tui/tui-io.c (tui_prep_terminal): Likewise.
> 	* tui/tui-win.c (tui_mouse): New global.
> 	(tui_set_mouse, tui_show_mouse_function): New functions.
> 	(_initialize_tui_win): Add mouse setting.
> 	* tui/tui-win.h (tui_mouse): Declare.
> 
> gdb/doc/ChangeLog:
> 
> 2021-06-07  Hannes Domani  <ssbssa@yahoo.de>
> 
> 	* gdb.texinfo (TUI Configuration): Document mouse setting.

OK for the documentation part.

  reply	other threads:[~2021-06-07 23:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210607163003.621-1-ssbssa.ref@yahoo.de>
2021-06-07 16:30 ` [PATCH 1/3] Refactor keypad calls to tui_set_win_focus_to Hannes Domani
2021-06-07 16:30   ` [PATCH 2/3] Disable mouse events if the command window has focos Hannes Domani
2021-06-07 16:30   ` [PATCH 3/3] Add setting to enable/disable TUI mouse handling Hannes Domani
2021-06-07 16:49     ` Eli Zaretskii [this message]
2021-06-17 14:54   ` [PATCH 1/3] Refactor keypad calls to tui_set_win_focus_to Hannes Domani

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=83mts1fwmr.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=ssbssa@yahoo.de \
    /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).