From: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Paredit, smartparens very slow with large latex files
Date: Fri, 20 Sep 2013 09:14:13 +0200 [thread overview]
Message-ID: <523BF5C5.1040404@easy-emacs.de> (raw)
In-Reply-To: <874n9k8o5u.fsf@free.fr>
Am 16.09.2013 23:14, schrieb Julien Cubizolles:
> Andreas Röhler <andreas.roehler@easy-emacs.de> writes:
>
>
>> Please tell the command-name tried from paredit.el.
>
> paredit-forward takes roughly half a second to go from
> \SI{10}{\meter\per\sec|ond} to \SI{10}{\meter\per\sec|ond}| in a large
> buffer. It's instantaneous in *scratch*
>
paredit-forward makes three stops with your example
start from sec|ond
\SI{10}{\meter\per\second}| to \SI{10}{\meter\per\second}
\SI{10}{\meter\per\second} to| \SI{10}{\meter\per\second}
\SI{10}{\meter\per\second} to \SI{10}{\meter\per\second}|
Seems not suitable at all to travel large buffers that way.
As it happens created a tool for this purposes:
ar-forward-braced-atpt
Checked it that way
\SI{10}{\meter\per\sec|ond}
;; fill in a number of "a" in buffer
(insert (make-string 999999 97)
;; than call ar-forward-braced-atpt from above
\SI{10}{\meter\per\second}
Get a reasonable delay as isearch-forward CHAR would have.
Command is available at
https://launchpad.net/s-x-emacs-werkstatt/
Preferably via bazaar
lp:s-x-emacs-werkstatt
next prev parent reply other threads:[~2013-09-20 7:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 9:59 Paredit, smartparens very slow with large latex files Julien Cubizolles
2013-09-11 13:38 ` Tim Visher
2013-09-11 15:58 ` Andreas Röhler
2013-09-12 20:36 ` Julien Cubizolles
2013-09-13 6:32 ` Andreas Röhler
2013-09-16 21:14 ` Julien Cubizolles
2013-09-20 7:14 ` Andreas Röhler [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-09-11 10:08 Vilibald Wanca
2013-09-12 20:27 ` Julien Cubizolles
2013-09-13 6:30 ` Andreas Röhler
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=523BF5C5.1040404@easy-emacs.de \
--to=andreas.roehler@easy-emacs.de \
--cc=help-gnu-emacs@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.