From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: YAMAMOTO Mitsuharu Newsgroups: gmane.emacs.devel Subject: Re: Emacs Mac port Date: Tue, 23 Apr 2013 12:18:33 +0900 Organization: Faculty of Science, Chiba University Message-ID: References: <83ip3p72mz.fsf@gnu.org> <83d2tw73h7.fsf@gnu.org> <8361zo6um1.fsf@gnu.org> <8338us6oz9.fsf@gnu.org> <838v4j55si.fsf@gnu.org> <871ua3oshi.fsf@spindle.srvr.nix> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Trace: ger.gmane.org 1366687125 4226 80.91.229.3 (23 Apr 2013 03:18:45 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 23 Apr 2013 03:18:45 +0000 (UTC) Cc: Eli Zaretskii , emacs-devel@gnu.org To: Nix Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Apr 23 05:18:49 2013 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1UUTkm-0006us-1x for ged-emacs-devel@m.gmane.org; Tue, 23 Apr 2013 05:18:48 +0200 Original-Received: from localhost ([::1]:58722 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UUTkl-0004YZ-Ii for ged-emacs-devel@m.gmane.org; Mon, 22 Apr 2013 23:18:47 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:43757) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UUTki-0004YS-EV for emacs-devel@gnu.org; Mon, 22 Apr 2013 23:18:45 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UUTkh-0000xz-D3 for emacs-devel@gnu.org; Mon, 22 Apr 2013 23:18:44 -0400 Original-Received: from mathmail.math.s.chiba-u.ac.jp ([133.82.132.2]:63801) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UUTke-0000wP-Bn; Mon, 22 Apr 2013 23:18:40 -0400 Original-Received: from church.math.s.chiba-u.ac.jp (church [133.82.132.36]) by mathmail.math.s.chiba-u.ac.jp (Postfix) with ESMTP id 2DDC8C055D; Tue, 23 Apr 2013 12:18:34 +0900 (JST) In-Reply-To: <871ua3oshi.fsf@spindle.srvr.nix> User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.3 (sparc-sun-solaris2.8) MULE/5.0 (SAKAKI) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 133.82.132.2 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:159140 Archived-At: >>>>> On Mon, 22 Apr 2013 09:54:33 +0100, Nix said: >>> Which window systems we support don't use "backing store"? >> >> Some implementations of Xservers. According to the manual, -bs >> option seems to turn off the backing store support. > This option does nothing nowadays, because backing store was > entirely removed from the X.org X server implementation before X > server 1.5, in 2007. The idea now is that if you want the same > effect you have to use a compositing manager, which naturally > provides double-buffering of everything anyway. >> Mac does have "backing store". I meant Xserver implementation >> without "backing store". I vaguely remember Xvnc didn't have one >> and issued "expose" events every time a window is uncovered, but >> I'm not sure about the recent situation of Xservers. > Just use X.org and make sure your compositing manager is turned off > :) Thanks for the info. With these hints, I could reproduce the problem on CentOS 5.9, where no compositing manager seems to be used by default and expose events are issued when a window is being uncovered. 1. Execute "emacs -Q -D &" from the terminal window. 2. Evaluate the following expression in the *scratch* buffer: (progn (sleep-for 5) (let ((cursor-in-echo-area t)) (message "foo") (sit-for 0)) (sleep-for 30)) 3. Switch focus to the terminal window and wait 5 seconds for the message "foo" followed by the cursor to be displayed in the echo area. 4. Move the terminal window so it goes across the echo area. Then the cursor in the echo area disappears. If I try the same experiment on Ubuntu 12.04 LTS, which has a compositing manager, then the cursor does not disappear. YAMAMOTO Mitsuharu mituharu@math.s.chiba-u.ac.jp