Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 11 Feb 1997 16:22:36 +1100
From:      David Nugent <davidn@labs.usn.blaze.net.au>
To:        Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
Cc:        Zach Heilig <zach@blizzard.gaffaneys.com>, freebsd-bugs@freebsd.org
Subject:   Re: moused and X11R6
Message-ID:  <19970211162236.64243@usn.blaze.net.au>
In-Reply-To: <199702110324.MAA00887@zodiac.mech.utsunomiya-u.ac.jp>; from Kazutaka YOKOTA on Feb 02, 1997 at 12:24:23PM
References:  <876804rsia.fsf@murkwood.gaffaneys.com> <Pine.BSF.3.95.970207222919.2151A-100000@chaos.ecpnet.com> <19970208165555.12961@usn.blaze.net.au> <87bu9venx6.fsf@murkwood.gaffaneys.com> <19970208201732.37402@usn.blaze.net.au> <87g1z47bc6.fsf@murkwood.gaffaneys.com> <199702110324.MAA00887@zodiac.mech.utsunomiya-u.ac.jp>

next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 02, 1997 at 12:24:23PM, Kazutaka YOKOTA wrote:
> >
> >in the virtual terminal that was later used to run X.  Problems went
> >away after I thought of that and turned it off...
> 
> Hmmm. I experimented this; I did
> 
> vidcontrol -m on
> 
> in a virtual terminal, then from within the same terminal, I started X. 
> The X server switches to an unused virtual terminal (this is the way it
> works) and my mouse works fine there.  I switch back to the virtual
> terminal on which I run vidcontrol, the terminal shows some lines from
> the X server AND the mouse cursor.  I can move the mouse cursor and
> mark region in the screen with no problem.
> 
> I even did `vidcontrol -m on' in yet another virtual terminal, and it
> works. No conflicts.

No conflicts here either, fwiw - not with this scenario. I run
into it as a matter of course; my .profile/.login enable the
mouse if I'm on ttyv* (cut/paste is too useful, and now that
the mouse cursor disappears automatically, it isn't at all
intrusive). I run X often without first disabling the console
mouse.

I had assumed by "in the virtual terminal that was later used
to run X" meant the actual vt that X runs on (presumably after
it had been disabled), rather than the one from which it was
started. I can see how that might cause conflicts since it
would relate vt switching.


Regards,

David Nugent - Unique Computing Pty Ltd - Melbourne, Australia
Voice +61-3-9791-9547  Data/BBS +61-3-9792-3507  3:632/348@fidonet
davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970211162236.64243>