From: drain <aeuster@gmail.com>
To: Help-gnu-emacs@gnu.org
Subject: Re: recover file after crash
Date: Fri, 25 Jan 2013 13:04:23 -0800 (PST) [thread overview]
Message-ID: <1359147863880-276502.post@n5.nabble.com> (raw)
In-Reply-To: <83txq5j8mn.fsf@gnu.org>
Eli Zaretskii wrote
>> Date: Fri, 25 Jan 2013 12:31:57 -0800 (PST)
>> From: drain <
> aeuster@
> >
>>
>> In any case, I sent Valentin a large file that tends to lag
>
> If it has no or few empty lines, adding empty lines (e.g., before
> top-level headings) might dramatically improve performance in very
> large buffers.
I have to add a couple spaces to the very end of the text of the last
nested headline in order for the spaces to separate each of the top level
headlines. Otherwise, when I reopen the file, these spaces are gone.
In any case, after doing so, implementing your suggestion appears to have
improved performance, especially when sifting through top level headlines
that are partially or completely opened, and also especially when running
point rapidly up a sequence of top level headlines.
--
View this message in context: http://emacs.1067599.n5.nabble.com/recover-file-after-crash-tp276397p276502.html
Sent from the Emacs - Help mailing list archive at Nabble.com.
next prev parent reply other threads:[~2013-01-25 21:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 20:16 recover file after crash drain
2013-01-24 21:00 ` Drew Adams
2013-01-25 18:23 ` drain
2013-01-25 18:30 ` Valentin Baciu
2013-01-25 19:12 ` drain
2013-01-25 19:29 ` Eli Zaretskii
2013-01-25 20:31 ` drain
2013-01-25 20:44 ` Eli Zaretskii
2013-01-25 21:04 ` drain [this message]
2013-01-25 20:56 ` Ludwig, Mark
2013-01-26 10:39 ` Eli Zaretskii
2013-01-26 21:47 ` Ludwig, Mark
2013-01-27 6:19 ` Eli Zaretskii
[not found] ` <mailman.18392.1359236878.855.help-gnu-emacs@gnu.org>
2013-02-20 1:35 ` David Combs
2013-01-25 19:36 ` Valentin Baciu
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=1359147863880-276502.post@n5.nabble.com \
--to=aeuster@gmail.com \
--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.
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).