From xemacs-m  Mon May 12 05:00:11 1997
Received: from jagor.srce.hr (hniksic@jagor.srce.hr [161.53.2.130])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id FAA03014
	for <xemacs-beta@xemacs.org>; Mon, 12 May 1997 05:00:09 -0500 (CDT)
Received: (from hniksic@localhost)
          by jagor.srce.hr (8.8.5/8.8.4)
	  id MAA03855; Mon, 12 May 1997 12:00:03 +0200 (MET DST)
To: XEmacs Developers <xemacs-beta@xemacs.org>
Subject: Cursor on different frames, different devices
X-Save-Project-Gutenberg: <URL:http://www.promo.net/pg/nl/pgny_nov96.html>
X-Attribution: Hrv
X-Face: Mie8:rOV<\c/~z{s.X4A{!?vY7{drJ([U]0O=W/<W*SMo/Mv:58:*_y~ki>xDi&N7XG
        KV^$k0m3Oe/)'e%3=$PCR&3ITUXH,cK>]bci&<qQ>Ff%x_>1`T(+M2Gg/fgndU%k*ft
        [(7._6e0n-V%|%'[c|q:;}td$#INd+;?!-V=c8Pqf}3J
From: Hrvoje Niksic <hniksic@srce.hr>
Date: 12 May 1997 12:00:01 +0200
Message-ID: <kigsoztypr2.fsf@jagor.srce.hr>
Lines: 21
X-Mailer: Gnus v5.4.52/XEmacs 19.15

Here is an annoying behaviour I'd like to fix, once reported on
comp.emacs.xemacs.

Start `xemacs -nw', and use `M-x make-frame-on-display' to create an X
frame.  Try to move point on any of those frames, and you'll notice
that cursor movement is "locked" among the frames; any cursor
movements in the X frame results in the cursor movement on the TTY
frame, and vice versa.  This doesn't happen with multiple X frames.

Inspecting the matter shows that the cursor information is
console-local.  This is, of course, wrong, as it should be frame-local
(or window-local, or whatever).  The FORCE_CURSOR_UPDATE macro in
redisplay-tty.c takes a console argument.  Maybe I should update it to
take a frame arguments?

Can anyone help me out with this?

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
Ask not for whom the <CONTROL-G> tolls.

