From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Paul Eggert Newsgroups: gmane.emacs.devel Subject: Re: RFC: flicker-free double-buffered Emacs under X11 Date: Thu, 27 Oct 2016 19:07:09 -0700 Organization: UCLA Computer Science Department Message-ID: <57c7048e-a6d1-9908-0331-675073aa11e6@cs.ucla.edu> References: <9e8ad090-a6a0-c807-95ae-7ec7c3f391cb@dancol.org> <83k2d2rssf.fsf@gnu.org> <831sz9sime.fsf@gnu.org> <83y41hqz94.fsf@gnu.org> <838tte5fzq.fsf@gnu.org> <740d34db48a1e4b711cb1cfa987423c9.squirrel@dancol.org> <1706d8c5-118b-7d68-bd25-1f95b1787aa2@cs.ucla.edu> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1477626696 23272 195.159.176.226 (28 Oct 2016 03:51:36 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 28 Oct 2016 03:51:36 +0000 (UTC) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 Cc: emacs-devel@gnu.org To: Daniel Colascione Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Oct 28 05:51:32 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bzyC7-0002Gh-Js for ged-emacs-devel@m.gmane.org; Fri, 28 Oct 2016 05:51:03 +0200 Original-Received: from localhost ([::1]:46355 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bzyCA-00049I-A4 for ged-emacs-devel@m.gmane.org; Thu, 27 Oct 2016 23:51:06 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:39792) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bzwZj-0000hE-4X for emacs-devel@gnu.org; Thu, 27 Oct 2016 22:07:19 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bzwZf-0002Gw-6l for emacs-devel@gnu.org; Thu, 27 Oct 2016 22:07:19 -0400 Original-Received: from zimbra.cs.ucla.edu ([131.179.128.68]:55012) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1bzwZf-0002GT-0W for emacs-devel@gnu.org; Thu, 27 Oct 2016 22:07:15 -0400 Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id DDF8316106D; Thu, 27 Oct 2016 19:07:13 -0700 (PDT) Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id p1gHrNVeJBqV; Thu, 27 Oct 2016 19:07:13 -0700 (PDT) Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 2EAD016106F; Thu, 27 Oct 2016 19:07:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at zimbra.cs.ucla.edu Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id F7LerRexUHiC; Thu, 27 Oct 2016 19:07:13 -0700 (PDT) Original-Received: from [192.168.1.9] (unknown [47.153.178.162]) by zimbra.cs.ucla.edu (Postfix) with ESMTPSA id 0663E16106D; Thu, 27 Oct 2016 19:07:12 -0700 (PDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 131.179.128.68 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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" Xref: news.gmane.org gmane.emacs.devel:208908 Archived-At: Daniel Colascione wrote: > I've found the flickering while editing to be very machine-dependent...= . > I've found I can reliably reproduce the flickering by isearching for a > string that appears in a buffer only once, then leaning on C-s. Weird. I can't reproduce the flickering problem on either Fedora 24 GTK x= 86-64=20 or Ubuntu 16.04.1 GTK x86-64, even though I tried your recipe. I wonder w= hat's=20 different about my platforms? Anyway, if the code is fixing a real proble= m on=20 your platforms and doesn't cause trouble elsewhere, we should install it. > I'll feel more comfortable about removing the lisp interface (and so an= y > way for users to this the thing off) once we're sure it's not > causing problems. Perhaps mark it as deprecated so that the user knows it might go away? > if we're C99-only anyway now, we might as well allow > C99 comments. Maybe, but that would be a different topic, and should be addressed in a=20 separate patch. For example, we might also need to change our C-reading p= rograms.