From: "Randy W. Sims" <RandyS@ThePierianSpring.org>
Subject: Re: I seek QA for CPerl 5.2 (Emacs mode)
Date: Tue, 18 Oct 2005 22:14:21 -0400 [thread overview]
Message-ID: <4355ABFD.7020508@ThePierianSpring.org> (raw)
In-Reply-To: <dj41fi$2cal$1@agate.berkeley.edu>
Ilya Zakharevich wrote:
> [A complimentary Cc of this posting was sent to
> Randy W. Sims
> <RandyS@thepierianspring.org>], who wrote in article <435556D7.7030303@thepierianspring.org>:
>
>> One wierd problem I find is if I load two copies of a certain file it
>> becomes develishly slow to do anything, even scrolling. This doesn't
>> seem to happen on all files; not sure if it's size or content related yet.
>>
>> Eg, If I unpack the Module::Build distribution into two different
>> directories, then load copies of Module/Build/Base.pm from each
>> location, the second buffer becomes slow. The original buffer and any
>> others are not affected. If I close both buffers, then open the same
>> file again, the new buffer is also slow-I must exit emacs and restart
>> before I can work with that particular file because of slowdown.
>
>> This is on Debian (testing) with GNU Emacs 21.4.1.
>
> Confirmed on 21.2. This effect disappears if I switch to an older
> version of font-lock (e.g., one on
> ilyaz.org/software/tmp/font-lock-old.zip
> ). One does not need to load the same file or a large file; two files
> of size about 80K show the same slowdown in
> fontification-by-keywords. (I used Build.pm and Build/Base.pm.)
>
> Go to the ends of both buffers, then start to scroll back - it is
> painfully slow in one of the buffers...
>
> I have no idea how to debug this... My conjecture is that newer
> Font-lock somehow starts to think that it needs to fontify the full
> buffer instead of doing only the visible part...
Unfortunately, I don't know much lisp, so I can't help there. I did just
try it out on my Windows box with XEmacs 21.4.17, same emacs init file.
I see no sign of the above problem. The font-lock.el here is:
;; Copyright (C) 1992-1995, 1997 Free Software Foundation, Inc.
;; Copyright (C) 1995 Amdahl Corporation.
;; Copyright (C) 1996, 2000, 2001 Ben Wing.
;; Author: Jamie Zawinski <jwz@jwz.org>, for the LISPM Preservation Society.
;; Minimally merged with FSF 19.34 by Barry Warsaw <bwarsaw@python.org>
;; Then (partially) synched with FSF 19.30, leading to:
;; Next Author: RMS
;; Next Author: Simon Marshall <simon@gnu.ai.mit.edu>
;; Latest XEmacs Author: Ben Wing
;; Maintainer: XEmacs Development Team
;; Keywords: languages, faces
next prev parent reply other threads:[~2005-10-19 2:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-18 1:45 I seek QA for CPerl 5.2 (Emacs mode) Ilya Zakharevich
2005-10-18 20:11 ` Randy W. Sims
2005-10-18 23:45 ` Ilya Zakharevich
2005-10-19 2:14 ` Randy W. Sims [this message]
2005-10-19 0:43 ` Bug in font-lock? Was: QA for CPerl 5.2 Ilya Zakharevich
2005-10-19 7:16 ` I seek QA for CPerl 5.2 (Emacs mode) Ilya Zakharevich
[not found] ` <200510190716.j9J7GWWf021292@powdermilk.math.berkeley.edu>
2005-10-19 19:52 ` Randy W. Sims
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4355ABFD.7020508@ThePierianSpring.org \
--to=randys@thepierianspring.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).