From owner-freebsd-bugs Mon Feb 10 22:28:41 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA02163 for bugs-outgoing; Mon, 10 Feb 1997 22:28:41 -0800 (PST) Received: from nasu.utsunomiya-u.ac.jp (nasu.utsunomiya-u.ac.jp [160.12.128.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA02154 for ; Mon, 10 Feb 1997 22:28:38 -0800 (PST) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by nasu.utsunomiya-u.ac.jp (8.8.4+2.7Wbeta4/3.5Wpl3) with ESMTP id PAA15320; Tue, 11 Feb 1997 15:28:02 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (vN+FxGI555wpDtJDtFTkQwW4hGlVr4ZY@zodiac.mech.utsunomiya-u.ac.jp [160.12.33.1]) by outmail.utsunomiya-u.ac.jp (8.8.4+2.7Wbeta4/3.5Wpl3) with ESMTP id PAA30462; Tue, 11 Feb 1997 15:27:56 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.33.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id PAA06663; Tue, 11 Feb 1997 15:31:48 +0900 (JST) Message-Id: <199702110631.PAA06663@zodiac.mech.utsunomiya-u.ac.jp> To: freebsd-bugs@freebsd.org cc: David Nugent , Zach Heilig , yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: moused and X11R6 In-reply-to: Your message of "Tue, 11 Feb 1997 16:22:36 +1100." <19970211162236.64243@usn.blaze.net.au> References: <876804rsia.fsf@murkwood.gaffaneys.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> <19970211162236.64243@usn.blaze.net.au> Date: Tue, 11 Feb 1997 15:31:47 +0900 From: Kazutaka YOKOTA Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> 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. Well, but, is it possible to have `vidcontrol -m on' in the same virtual terminal as X? I thought not. The X server runs in an unused virtual terminal; UNUSED terminal being the one to which no login is possible because getty is not running in it, thus, we cannot have `vidcontrol -m on' there. Wait, I will check the XFree86 man page... Hmmm, with a command line option, the XFree86 X server can be instructed to run in a specific virtual terminal. Is this the scenario are we discussing here? Kazu