From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Juanma Barranquero Newsgroups: gmane.emacs.devel Subject: Re: Emacs 23, so slow to refresh on Windows Date: Tue, 18 May 2010 09:25:28 +0200 Message-ID: References: <8CCC3DAB0774A32-16F0-1536@web-mmc-d09.sysops.aol.com> <8CCC4332DEEAEEC-16F0-3DA0@web-mmc-d09.sysops.aol.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: dough.gmane.org 1274170847 27013 80.91.229.12 (18 May 2010 08:20:47 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 18 May 2010 08:20:47 +0000 (UTC) Cc: emacs-devel@gnu.org To: bogossian@mail.com Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue May 18 10:20:45 2010 connect(): No such file or directory 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.69) (envelope-from ) id 1OEI2b-0000Xd-FA for ged-emacs-devel@m.gmane.org; Tue, 18 May 2010 10:20:45 +0200 Original-Received: from localhost ([127.0.0.1]:46379 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OEI2Y-0002X2-W1 for ged-emacs-devel@m.gmane.org; Tue, 18 May 2010 04:20:39 -0400 Original-Received: from [140.186.70.92] (port=46950 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OEHDl-0007Jw-VU for emacs-devel@gnu.org; Tue, 18 May 2010 03:31:52 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OEHBV-0007ax-If for emacs-devel@gnu.org; Tue, 18 May 2010 03:28:08 -0400 Original-Received: from mail-fx0-f41.google.com ([209.85.161.41]:36760) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OEHBV-0007af-89 for emacs-devel@gnu.org; Tue, 18 May 2010 03:25:49 -0400 Original-Received: by fxm20 with SMTP id 20so4263662fxm.0 for ; Tue, 18 May 2010 00:25:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type; bh=YAFz7vuOF05cMUx/R1iP4ymttAEAF2KKMlg6fB2YNBA=; b=SKDeqFIYhemtvvJvncLYTaMHTJLUg1WOQ+Sc5IzjmIVY1k4JAK9yDwY/MsIez1pcz3 v7vl1Hnd66JKb9adqK2/gjMDbiFpyy2WhMaiiJMDTbSjcIj5hjMhPr3ANwZVQ6YT1RPK nCH+7JLTCmfnNYP9boH1n2vm7ySEph+DhEkeI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=rjQndiJfGwRtSkxX/h1f279S8fr7dyz5W6dXlmw42B/i8/SnkEWhKJNn5+MJLrDb6d KcckSDh5SKy0D4/rZxQtYyWgM+94xybrDDTEGAm7ZNgKwKfr52LA1u54SW966q+2a8as pSw8pQ8eV0A2mkDMW2oF4Go7pYL+SQSntP5G0= Original-Received: by 10.204.156.5 with SMTP id u5mr133620bkw.161.1274167548107; Tue, 18 May 2010 00:25:48 -0700 (PDT) Original-Received: by 10.204.74.70 with HTTP; Tue, 18 May 2010 00:25:28 -0700 (PDT) In-Reply-To: <8CCC4332DEEAEEC-16F0-3DA0@web-mmc-d09.sysops.aol.com> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) 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:124881 Archived-At: On Tue, May 18, 2010 at 01:52, wrote: > No, I've done more testing and so far I haven't noticed any slowdown with > normal files (ie. files without long lines). > So, I think we can assume the performance issue is specific to files with > long lines. Assuming you use continuation lines, and not truncation, does the speed improve setting `cache-long-line-scans' to t? (Note that the variable is automatically buffer-local, so be sure to set it in the appropriate buffer, or use setq-default.) > With the 6x13 font, it doesn't make a difference (6x13 being a bitmap > font, I suppose it's always rendered using the gdi backend). Yes, I think so. You can see the backend used for a font by moving the cursor over a character in that font and doing "C-u C-x =". The font information will start with gdi: or uniscribe: > And I'm probably not the only > one who has to deal with computer generated files (dumps, logs, export > files, ...) containing very long lines. No, that is indeed very common. Juanma