From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Jason Rumney Newsgroups: gmane.emacs.devel,gmane.emacs.pretest.bugs Subject: Re: 23.0.60; show-paren-mode causes abnormal vertical lines on Win32. Date: Fri, 15 Feb 2008 23:16:58 +0000 Message-ID: <47B61D6A.3070004@gnu.org> References: <8463wrm4ls.fsf@gmail.com> <47B55785.8030802@gnu.org> <47B607C6.20601@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1203117445 15489 80.91.229.12 (15 Feb 2008 23:17:25 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 15 Feb 2008 23:17:25 +0000 (UTC) Cc: emacs-pretest-bug@gnu.org To: Juanma Barranquero Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Feb 16 00:17:48 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JQ9oO-00036i-63 for ged-emacs-devel@m.gmane.org; Sat, 16 Feb 2008 00:17:44 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JQ9nt-0004ZR-Tg for ged-emacs-devel@m.gmane.org; Fri, 15 Feb 2008 18:17:13 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JQ9no-0004W9-Ud for emacs-devel@gnu.org; Fri, 15 Feb 2008 18:17:08 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JQ9nn-0004Sz-68 for emacs-devel@gnu.org; Fri, 15 Feb 2008 18:17:08 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JQ9nn-0004Sp-1r for emacs-devel@gnu.org; Fri, 15 Feb 2008 18:17:07 -0500 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JQ9nm-0005MA-Pz for emacs-devel@gnu.org; Fri, 15 Feb 2008 18:17:06 -0500 Original-Received: from mx10.gnu.org ([199.232.76.166]) by fencepost.gnu.org with esmtp (Exim 4.67) (envelope-from ) id 1JQ9nm-0001rc-K5 for emacs-pretest-bug@gnu.org; Fri, 15 Feb 2008 18:17:06 -0500 Original-Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1JQ9nj-0005Ls-GJ for emacs-pretest-bug@gnu.org; Fri, 15 Feb 2008 18:17:06 -0500 Original-Received: from mk-outboundfilter-4.mail.uk.tiscali.com ([212.74.114.32]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JQ9nj-0005Lm-6L for emacs-pretest-bug@gnu.org; Fri, 15 Feb 2008 18:17:03 -0500 Original-X-Trace: 7112558/mk-outboundfilter-2.mail.uk.tiscali.com/F2S/$ACCEPTED/freedom2Surf-customers/83.67.23.108 X-SBRS: None X-RemoteIP: 83.67.23.108 X-IP-MAIL-FROM: jasonr@gnu.org X-IP-BHB: Once X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAAHestUdTQxds/2dsb2JhbAAIrjc X-IronPort-AV: E=McAfee;i="5200,2160,5231"; a="7112558" X-IronPort-AV: E=Sophos;i="4.25,360,1199664000"; d="scan'208";a="7112558" X-IP-Direction: OUT Original-Received: from i-83-67-23-108.freedom2surf.net (HELO [127.0.0.1]) ([83.67.23.108]) by smtp.f2s.tiscali.co.uk with ESMTP/TLS/DHE-RSA-AES256-SHA; 15 Feb 2008 23:17:02 +0000 User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) In-Reply-To: X-detected-kernel: by monty-python.gnu.org: Genre and OS details not recognized. X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:89191 gmane.emacs.pretest.bugs:21121 Archived-At: Juanma Barranquero wrote: > On Feb 15, 2008 10:44 PM, Jason Rumney wrote: > > >> And the old code will >> be removed if I understand correctly, so what point is there in fixing >> minor bugs in it now? >> > > As I see it, that is an argument for making the new backend the > default now, not "before the release of 23.1"... > There are also arguments against that, such as the fact that the new backend does not seem to have stabilised yet, with problems like Stefan is experiencing now, and which Windows users suffered around the time of the merge still a frequent occurrence.