all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tim Visher <tim.visher@gmail.com>
To: Julien Cubizolles <j.cubizolles@free.fr>
Cc: emacs <help-gnu-emacs@gnu.org>
Subject: Re: Paredit, smartparens very slow with large latex files
Date: Wed, 11 Sep 2013 09:38:14 -0400	[thread overview]
Message-ID: <CAHa53uxMS=0qKyYyP=SgwfTe_xLS6yYt6QaZnPp2YGMWa3bD8Q@mail.gmail.com> (raw)
In-Reply-To: <87ioy7vfv1.fsf@free.fr>

I've been told several times that any slow-down in emacs based on the
size of the buffer that is below `large-file-warning-threshold` should
be considered a bug. If Fundamental mode doesn't exhibit the problem,
I'd file a bug report with the maintainers of the package.

On Wed, Sep 11, 2013 at 5:59 AM, Julien Cubizolles <j.cubizolles@free.fr> wrote:
> All the minor modes I've tried to navigate through sexps are very slow
> when working with large latex files (>1000 lines). For example
> sp-forward-sexp takes several seconds to do the following:
> \(|\) -> \(\)| whereas it's instantaneous in a small buffer. Is there a
> way to improve things ? I tried folding parts of the buffer but it
> doesn't help since the folded part is still parsed.
>
> Julien.
>
>



  reply	other threads:[~2013-09-11 13:38 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 [this message]
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
  -- 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='CAHa53uxMS=0qKyYyP=SgwfTe_xLS6yYt6QaZnPp2YGMWa3bD8Q@mail.gmail.com' \
    --to=tim.visher@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=j.cubizolles@free.fr \
    /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.