unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ergus <spacibba@aol.com>
Cc: emacs-devel@gnu.org
Subject: Re: Mouse information in xterm.
Date: Mon, 14 Sep 2020 22:14:15 +0300	[thread overview]
Message-ID: <838sdc9nnc.fsf@gnu.org> (raw)
In-Reply-To: <20200914190453.wcnptz344vju6msx@Ergus> (message from Ergus on Mon, 14 Sep 2020 21:04:53 +0200)

> Date: Mon, 14 Sep 2020 21:04:53 +0200
> From: Ergus <spacibba@aol.com>
> Cc: emacs-devel@gnu.org
> 
> On Mon, Sep 14, 2020 at 09:56:37PM +0300, Eli Zaretskii wrote:
> >> Date: Mon, 14 Sep 2020 20:13:11 +0200
> >> From: Ergus <spacibba@aol.com>
> >> Cc: emacs-devel@gnu.org
> >>
> >> When we call x-popup-dialog with t as the first parameter. The function
> >> x_popup_menu_1 tries to get the cursor/mouse position calling
> >> term_mouse_position. (As the documentation says)
> >>
> >> The issue is that term_mouse_position always report (0,0) as the current
> >> position independently of the cursor and mouse actual positions because
> >> it just copies the values in last_mouse_x and last_mouse_y which are
> >> zero because nobody updated them, see.
> >
> >last_mouse_x and last_mouse_y will change only if you use GPM mouse on
> >the terminal.  Otherwise, these variables will remain zero on
> >GNU/Linux.  So what you see is expected unless you use GPM (do you?).
> >
> >The doc string of x-popup-dialog says that if POSITION is t, then the
> >dialog appears at the center of the selected frame.  So what you see
> >is exactly what the documentation says, and I don't understand what is
> >the problem you are trying to solve, or why POSITION being t is
> >important to you, or where you expected or wanted the dialog to pop up
> >or why there.  Please elaborate, as I feel we are talking past each
> >other.
> >
> >I see the same on a GUI frame, btw, so I also don't understand what
> >"works as expected in gui" for you.
> >
> >What am I missing?
> >
> x-popup-menu manual says:

Are we talking about x-popup-menu or x-popup-dialog?  You talked about
the latter in all your messages.

So I'm still confused...

> The part of "if the mouse is not available on a text terminal" then
> doesn't apply to xterm with xterm-mouse-mode? 

Indeed, it doesn't.  Because AFAIK no one has yet adapted the TTY
menus and dialogs to xterm-mouse-mode.



  reply	other threads:[~2020-09-14 19:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200914113816.562wa5cwqxdtwnmy.ref@Ergus>
2020-09-14 11:38 ` Mouse information in xterm Ergus
2020-09-14 15:23   ` Eli Zaretskii
2020-09-14 16:27     ` Ergus
2020-09-14 17:34       ` Eli Zaretskii
2020-09-14 18:13         ` Ergus
2020-09-14 18:56           ` Eli Zaretskii
2020-09-14 19:04             ` Ergus
2020-09-14 19:14               ` Eli Zaretskii [this message]
2020-09-14 19:45                 ` Ergus

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=838sdc9nnc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=spacibba@aol.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).