unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 45834@debbugs.gnu.org
Subject: bug#45834: 28.0.50; Mouse events in terminal emacs
Date: Wed, 08 Sep 2021 12:51:01 +0300	[thread overview]
Message-ID: <83y287mm4a.fsf@gnu.org> (raw)
In-Reply-To: <87pmtj1kdv.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed,  08 Sep 2021 11:34:04 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: 45834@debbugs.gnu.org
> Date: Wed, 08 Sep 2021 11:34:04 +0200
> 
> Poking at this a bit more -- the translation of these events apparently
> relied on some magic in `read-event':
> 
>     ;; These translation functions actually call the focus handlers            
>     ;; internally and return an empty sequence, causing us to go on to         
>     ;; read the next event.                                                    
>     (define-key map "\e[I" #'xterm-translate-focus-in)
> 
> ;; By returning an empty key sequence, these two functions perform the         
> ;; moral equivalent of the kind of transparent event processing done           
> ;; by read-event's handling of special-event-map, but inside                   
> ;; read-key-sequence (which can recognize multi-character terminal             
> ;; notifications) instead of read-event (which can't).                         
> 
> (defun xterm-translate-focus-in (_prompt)
>   (setf (terminal-parameter nil 'tty-focus-state) 'focused)
>   (funcall after-focus-change-function)
>   [])
> 
> This works in Emacs 26.1, but not Emacs 27.1.

Meaning what? that xterm-translate-focus-in is no longer being called?
But you said up-thread that the handler _is_ being called.





  reply	other threads:[~2021-09-08  9:51 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-12 23:29 bug#45834: 28.0.50; Mouse events in terminal emacs Brady
2021-01-19  6:38 ` Lars Ingebrigtsen
2021-01-19  8:24   ` Eli Zaretskii
2021-01-19 15:22     ` Lars Ingebrigtsen
2021-01-19 15:38       ` Eli Zaretskii
2021-01-19 15:41         ` Lars Ingebrigtsen
2021-09-08  9:34           ` Lars Ingebrigtsen
2021-09-08  9:51             ` Eli Zaretskii [this message]
2021-09-08  9:54               ` Lars Ingebrigtsen
2021-09-08 13:07                 ` Eli Zaretskii
2021-09-08 13:24                   ` Lars Ingebrigtsen
2021-09-08 13:28                     ` Eli Zaretskii
2021-09-08 13:32                       ` Lars Ingebrigtsen
2021-09-08 13:34                       ` Eli Zaretskii
2021-09-08 13:41                         ` Lars Ingebrigtsen
2021-09-08 13:52                           ` Eli Zaretskii
2021-09-08 14:22                             ` Lars Ingebrigtsen
2021-09-08 15:49                             ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-08 16:04                               ` Eli Zaretskii
2021-09-09  2:22                                 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-09  6:30                                   ` Eli Zaretskii
2021-09-09 18:54                                     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-09 14:34                                   ` Lars Ingebrigtsen
2021-09-09 18:56                                     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-08 16:06                               ` Lars Ingebrigtsen

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=83y287mm4a.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=45834@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    /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).