From: David Kastrup <dak@gnu.org>
Cc: "Thien-Thi Nguyen" <ttn@gnu.org>,
Arne =?utf-8?Q?J=C3=B8rgensen?= <arne@arnested.dk>,
emacs-devel@gnu.org
Subject: Re: latexenc-find-file-coding-system is slow.
Date: Sat, 30 Apr 2005 10:08:29 +0200 [thread overview]
Message-ID: <8564y43cw2.fsf@lola.goethe.zz> (raw)
In-Reply-To: <87u0lpye89.fsf_-_@xs4all.nl> (Lute Kamstra's message of "Fri, 29 Apr 2005 14:11:34 +0200")
Lute Kamstra <Lute.Kamstra.lists@xs4all.nl> writes:
> Thien-Thi Nguyen <ttn@gnu.org> writes:
>
>> Arne Jørgensen <arne@arnested.dk> writes:
>>
>>> Richard Stallman <rms@gnu.org> wrote March 4, 2005:
>>>
>>> > We can now install them. Could you send me the
>>> > latest version of your changes, with change log
>>> > entries?
>>>
>>> So now I'm trying to post to list
>>
>> i have installed the files w/ the suggested names;
>> only modification was to re-indent latexenc.el.
>
> Since this change, opening a 117k .texi file takes seconds. It used
> to take a fraction of a second. I did a debug-on-quit during the wait
> a couple of times and that consistently gave me one of these two
> backtraces:
>
> Debugger entered--Lisp error: (quit)
> re-search-forward("^[^%$]*\\inputencoding{\\(.*\\)}" nil t)
>
> Debugger entered--Lisp error: (quit)
> re-search-forward("^[^%$]*\\usepackage\\[\\(.*\\)\\]{inputenc}" nil t)
>
> I guess the re-searching in latexenc-find-file-coding-system needs to
> be improved.
It simply needs to get limited: if the string is not in the first 3k
or so, don't look further for it.
However, if a 117k file already takes seconds, this also is a sign
that the regular expressions are faulty (even searching the whole file
should not take seconds at this size). And it certainly is a bug that
the inverted character range contains $ instead of \n: $ is not
special in the expression.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2005-04-30 8:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1D7MTJ-0002Jj-BJ@fencepost.gnu.org>
2005-04-26 12:07 ` Your Emacs changes Arne Jørgensen
2005-04-28 11:58 ` Thien-Thi Nguyen
2005-04-29 12:11 ` latexenc-find-file-coding-system is slow. (was: Your Emacs changes) Lute Kamstra
2005-04-29 14:57 ` latexenc-find-file-coding-system is slow Arne Jørgensen
2005-04-29 15:48 ` Lute Kamstra
2005-04-29 16:13 ` Stefan Monnier
[not found] ` <877jil8rz5.fsf@arnested.dk>
2005-04-29 17:19 ` Lute Kamstra
2005-04-30 8:08 ` David Kastrup [this message]
2005-05-01 11:08 ` Lute Kamstra
2005-05-01 12:07 ` latexenc-find-file-coding-system is slow. (was: Your Emacs changes) Richard Stallman
[not found] ` <871x8m96p6.fsf@arnested.dk>
2005-05-11 11:48 ` latexenc-find-file-coding-system is slow Lute Kamstra
2005-05-11 17:21 ` Arne Jørgensen
2005-05-11 23:07 ` Lute Kamstra
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=8564y43cw2.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=arne@arnested.dk \
--cc=emacs-devel@gnu.org \
--cc=ttn@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).