all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: emacs-devel@gnu.org
Subject: GPM and mouse highlight
Date: Sun, 29 Aug 2010 01:39:34 -0400	[thread overview]
Message-ID: <E1OpacA-0004CR-9b@fencepost.gnu.org> (raw)

A text terminal with a GPM mouse can support mouse highlight.
However, the implementation of this support in term.c uses static
variables to track the highlighted region.  Unless I'm missing
something, this means that this support cannot be available on more
than one terminal device at the same time, even though we have
multi-tty support for quite some time.

By contrast, the GUI sessions (and the MS-DOS port) have these
variables as part of the Display_Info structure and can track several
frames/devices independently.

Questions:

1) Is there some fundamental limitation of GPM that prevents it from
supporting more than a single device at a time?

2) If the answer to the previous question is NO, then should we add
the mouse-highlight related variables to struct tty_display_info on
Unix as well?

I'm asking because, as part of working on mouse highlight of
bidirectional text, I found out that there are 3 separate
implementations of mouse highlight: one for when we
HAVE_WINDOW_SYSTEM, another one for GPM, and yet another for MS-DOS.
Due to this, bugs that were fixed in the GUI version of this support
(e.g., bug#1220) are still there in the other 2 versions.  I'd like to
merge all 3 implementations into a single one.  (If nothing else, it
will save me from writing 3 very similar implementations of bidi-aware
mouse highlighting.)



             reply	other threads:[~2010-08-29  5:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-29  5:39 Eli Zaretskii [this message]
2010-08-29  8:30 ` GPM and mouse highlight Jan Djärv
2010-08-29 11:34   ` Eli Zaretskii
2010-08-29 12:34     ` Jan Djärv
2010-08-29 13:43       ` Eli Zaretskii
2010-08-30 15:52         ` Stefan Monnier

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=E1OpacA-0004CR-9b@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.