[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Two little features (and a bounty?)

From: Trent W. Buck
Subject: Re: Two little features (and a bounty?)
Date: Fri, 25 Jul 2008 17:52:51 +1000
User-agent: Mutt/1.5.18 (2008-05-17)

On Fri, Jul 25, 2008 at 12:42:25AM -0700, Micah Cowan wrote:
> Hash: SHA1
> Trent W. Buck wrote:
> > On Thu, Jul 24, 2008 at 10:36:02PM -0700, Micah Cowan wrote:
> >> The question is whether it can tell them _to_ send their events. And
> >> yes, that's accurate: a program that sends the "send mouse events"
> >> sequence to screen will have them passed along to other terms -
> >> provided that screen itself detects that it is being run in a
> >> mouse-capable display (determined by checking for the presence of
> >> either "xterm" or "rxvt" in the TERM value).
> > 
> > Please clarify: what are the semantics when using screen -x, say with
> > one TERM=xterm and one TERM=linux ?
> The one with TERM=xterm will get the mouse-enable sequence passed
> through to it (assuming it was attached at the time that sequence was
> sent); the TERM=linux one won't.

Would it be better to have screen "remember" if an enable sequence was
sent, so that if I *later* do

    xterm -e screen -xRR

the *new* xterm will also know about mousiness?  (IIUC, currently the
xterm has to be connected when you do M-x xterm-mouse-mode.)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]