From: "João Távora" <joaotavora@gmail.com>
To: 5734@debbugs.gnu.org
Subject: bug#5734: Fwd: 23.1.94; (forward-sexp N) at the very end of large latex-mode buffer takes time proportional to N
Date: Thu, 25 Mar 2010 20:54:06 +0100 [thread overview]
Message-ID: <1D21EF7D-A103-48F3-93DF-239440762783@gmail.com> (raw)
In-Reply-To: <m2y6hq1u71.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3512 bytes --]
Forgot to cc the bug db.
Begin forwarded message:
> From: João Távora <joaotavora@gmail.com>
> Date: March 25, 2010 8:52:47 PM GMT+01:00
> To: Chong Yidong <cyd@stupidchicken.com>
> Subject: Re: 23.1.94; (forward-sexp N) at the very end of large latex-mode buffer takes time proportional to N
>
> What about this? This was the workaround I used in autopair.el. The
> idea behind is that if one `latex-forward-sexp-1' went nowhere, the
> next one probably isn't going to. I may be wrong :-)
>
> === modified file 'lisp/textmodes/tex-mode.el'
> --- lisp/textmodes/tex-mode.el 2010-02-16 02:42:03 +0000
> +++ lisp/textmodes/tex-mode.el 2010-03-25 19:42:59 +0000
> @@ -1651,9 +1651,12 @@
> "Like `forward-sexp' but aware of multi-char elements and escaped parens."
> (interactive "P")
> (unless arg (setq arg 1))
> - (let ((pos (point)))
> + (let ((pos (point))
> + (prev-pos 0))
> (condition-case err
> - (while (/= arg 0)
> + (while (and (not (eq prev-pos (point)))
> + (/= arg 0))
> + (setq prev-pos (point))
> (setq arg
> (if (> arg 0)
> (progn (latex-forward-sexp-1) (1- arg))
>
> PS: I hadn't realised that `tex-mode' defines a `forward-sexp-function'
> hence my ignorant comment about the problem being in syntax.c's scan_list.
>
> Bye,
> João
>
> On Mar 25, 2010, at 8:17 PM, Chong Yidong wrote:
>
> start with `emacs -Q'
> M-x eval-expression RET (insert (make-string 100000 ?a)) RET
> M-x eval-expression RET (latex-mode) RET
> M-x eval-expression RET (forward-sexp 200) RET
> M-x eval-expression RET (forward-sexp 500) RET
> M-x eval-expression RET (forward-sexp (point-max)) RET
>
> In some versions of emacs this does not happen, notably my earlier
> Carbon Emacs "GNU Emacs 22.3.1 (i386-apple-darwin9.7.0, Carbon Version
> 1.6.0) of 2009-07-26 on gs674-seijiz.local" after loading some lisp
> libraries (don't know which), like the ones I have bellow (autopair,
> yasnippet).
>
> I can reproduce this slowness even on Emacs 22.3. It arises because
> tex-mode wants to be able to signal an error if point is in a containing
> expression that ends prematurely, so it does a bit of backtracking.
> (This is the `skip-syntax-backward' call in latex-forward-sexp-1).
>
> I'm not sure what the best way to fix this is, though.
> On Mar 25, 2010, at 8:17 PM, Chong Yidong wrote:
>
>>> start with `emacs -Q'
>>> M-x eval-expression RET (insert (make-string 100000 ?a)) RET
>>> M-x eval-expression RET (latex-mode) RET
>>> M-x eval-expression RET (forward-sexp 200) RET
>>> M-x eval-expression RET (forward-sexp 500) RET
>>> M-x eval-expression RET (forward-sexp (point-max)) RET
>>
>>> In some versions of emacs this does not happen, notably my earlier
>>> Carbon Emacs "GNU Emacs 22.3.1 (i386-apple-darwin9.7.0, Carbon Version
>>> 1.6.0) of 2009-07-26 on gs674-seijiz.local" after loading some lisp
>>> libraries (don't know which), like the ones I have bellow (autopair,
>>> yasnippet).
>>
>> I can reproduce this slowness even on Emacs 22.3. It arises because
>> tex-mode wants to be able to signal an error if point is in a containing
>> expression that ends prematurely, so it does a bit of backtracking.
>> (This is the `skip-syntax-backward' call in latex-forward-sexp-1).
>>
>> I'm not sure what the best way to fix this is, though.
>
[-- Attachment #2: Type: text/html, Size: 7305 bytes --]
next prev parent reply other threads:[~2010-03-25 19:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <72E45B8A-4496-440D-9D38-F9280DE76397@gmail.com>
2010-03-17 22:04 ` bug#5734: 23.1.94; (forward-sexp N) at the very end of large latex-mode buffer takes time proportional to N Joao Tavora
2010-03-25 19:17 ` Chong Yidong
2010-03-25 19:54 ` João Távora [this message]
2012-08-03 2:30 ` bug#5734: Fwd: " Chong Yidong
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=1D21EF7D-A103-48F3-93DF-239440762783@gmail.com \
--to=joaotavora@gmail.com \
--cc=5734@debbugs.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).