unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: csant <csant@csant.info>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: [multi-tty] xt-mouse.el does not work in emacsclient frames
Date: Fri, 18 May 2007 14:57:51 -0700	[thread overview]
Message-ID: <200705182157.l4ILvpj0027509@oogie-boogie.ics.uci.edu> (raw)
In-Reply-To: <op.tsjk70ked84skq@fiore.malebolge> (csant@csant.info's message of "Fri\, 18 May 2007 23\:41\:50 +0200")

csant <csant@csant.info> writes:

  > >   > emacs -Q -nw
  > >   > M-x server-start RET
  > >   > M-x xterm-mouse-mode RET
  > >
  > > This will turn on xterm-mouse-mode for the "emacs -Q -nw" frame
  > >
  > >   > emacsclient -t
  > >
  > > it won't turn it on for this one.
  > 
  > Not sure that's right: 

It is. emacs needs to send an escape sequence to xterm so that xterm
can start sending mouse tracking events. Nothing is doing it for the
"emacsclient -t" frame. Please check the code.


 > the mouse will pass some events to the client -  
  > they just get translated wrongly. Running M-x xterm-mouse-mode RET in
  > the  client *disables* xterm-mouse-mode, so I'd definetly say it is
  > running.

That's normal, you've turned it on (ie. the xterm-mouse-mode is set to
t) then you previously run M-x xterm-mouse-mode RET in the "emacs -Q
-nw" frame. 

Since you have an interest in this, do you want to take a stab at
getting this working correctly for multi-tty? 

  reply	other threads:[~2007-05-18 21:57 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-16 22:49 [multi-tty] Odd regression in vcursor mode in terminal csant
2007-05-16 22:58 ` David Kastrup
2007-05-17  0:44 ` Dan Nicolaescu
2007-05-17  7:01   ` csant
2007-05-18 17:27   ` [multi-tty] xt-mouse.el does not work in emacsclient frames (was Re: Odd regression in vcursor mode in terminal) csant
2007-05-18 20:17     ` Dan Nicolaescu
2007-05-18 20:43       ` [multi-tty] xt-mouse.el does not work in emacsclient frames csant
2007-05-18 20:55         ` Dan Nicolaescu
2007-05-18 21:13           ` csant
2007-05-18 21:21             ` Dan Nicolaescu
2007-05-18 21:41               ` csant
2007-05-18 21:57                 ` Dan Nicolaescu [this message]
2007-05-18 21:59                 ` csant
2007-05-19  1:04             ` Robert J. Chassell
2007-05-19  2:12               ` Dan Nicolaescu
2007-05-19  2:28                 ` Dan Nicolaescu
2007-05-19 14:03                 ` Stefan Monnier
2007-05-19 16:00                   ` csant
2007-05-19 18:50                   ` David Kastrup
2007-05-21 12:39                     ` Stefan Monnier
2007-05-21 13:02                       ` David Kastrup
2007-05-21 14:12                         ` Stefan Monnier
2007-05-20 17:31 ` [multi-tty] Odd regression in vcursor mode in terminal Karoly Lorentey
2007-05-20 17:31 ` Karoly Lorentey

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=200705182157.l4ILvpj0027509@oogie-boogie.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=csant@csant.info \
    --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 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).