unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jared Finder via "Emacs development discussions." <emacs-devel@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: joaotavora@gmail.com, emacs-devel@gnu.org
Subject: Re: Mouse-hovering over 'mouse-face' overlays/regions on a TTY Emacs
Date: Fri, 15 Jan 2021 21:31:59 -0800	[thread overview]
Message-ID: <6d7d75bbad978a2eb8a80a7c90a33040@finder.org> (raw)
In-Reply-To: <91a58d2052f11b5f01a6ce41ebe93380@finder.org>

It seems like these set of patches got lost. Joao, Eli, is this no 
longer valuable?

   -- MJF

On 2020-12-07 9:46 pm, Jared Finder wrote:
> On 2020-12-05 2:39 am, Eli Zaretskii wrote:
>>> Date: Wed, 02 Dec 2020 00:40:01 -0800
>>> From: Jared Finder <jared@finder.org>
>>> Cc: joaotavora@gmail.com, emacs-devel@gnu.org
>>> 
>>> * src/frame.c (Fset_mouse_position, Fset_mouse_pixel_position): Call
>>> Fselect_frame in all terminals, independent of defines.
>> 
>> Maybe I'm missing something, but I don't see how the proposed changes
>> cause Fselect_frame to be called fore any display type.
> 
> Perhaps I'm using the wrong terminology?  It causes Fselect_frame to
> be called for all terminals, a.k.a *non-graphical* displays, a.k.a.
> the display you get when you specify -nw.
> 
> Other comments addressed, patch attached.
> 
>   -- MJF



  reply	other threads:[~2021-01-16  5:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-29 21:33 Mouse-hovering over 'mouse-face' overlays/regions on a TTY Emacs João Távora
2020-11-30  3:28 ` Eli Zaretskii
2020-11-30  8:21   ` João Távora
2020-11-30 16:09     ` Eli Zaretskii
2020-11-30 16:25       ` João Távora
2020-11-30 16:43         ` Eli Zaretskii
2020-11-30 16:47           ` João Távora
2020-11-30 18:05           ` João Távora
2020-11-30 18:24             ` Eli Zaretskii
2020-11-30 18:28               ` João Távora
2020-11-30 18:58                 ` Eli Zaretskii
2020-11-30 19:09                   ` João Távora
2020-11-30 20:07                     ` Stefan Monnier
2020-12-01  7:10                     ` Jared Finder via Emacs development discussions.
2020-12-01 18:20                       ` Eli Zaretskii
2020-12-02  8:40                         ` Jared Finder via Emacs development discussions.
2020-12-05 10:39                           ` Eli Zaretskii
2020-12-08  5:46                             ` Jared Finder via Emacs development discussions.
2021-01-16  5:31                               ` Jared Finder via Emacs development discussions. [this message]
2021-01-16  7:53                                 ` Eli Zaretskii
2021-01-16 13:06                                   ` Eli Zaretskii
2021-01-16 22:27                                     ` jared--- via Emacs development discussions.
2021-01-22 12:20                                       ` Eli Zaretskii
2021-01-22 16:47                                         ` João Távora

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6d7d75bbad978a2eb8a80a7c90a33040@finder.org \
    --to=emacs-devel@gnu.org \
    --cc=eliz@gnu.org \
    --cc=jared@finder.org \
    --cc=joaotavora@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).