From: Nick Dokos <nicholas.dokos@hp.com>
To: =?utf-8?Q?Fran=C3=A7ois?= Pinard <pinard@iro.umontreal.ca>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: Weight of headers
Date: Sun, 26 Feb 2012 23:12:31 -0500 [thread overview]
Message-ID: <25809.1330315951@alphaville> (raw)
In-Reply-To: Message from pinard@iro.umontreal.ca (=?utf-8?Q?Fran=C3=A7ois?= Pinard) of "Sun\, 26 Feb 2012 22\:56\:32 EST." <87wr79kjyn.fsf@iro.umontreal.ca>
François Pinard <pinard@iro.umontreal.ca> wrote:
> pinard@iro.umontreal.ca (François Pinard) writes:
>
> > Roughly copying code from here and there (and not even understanding it,
> > some dead code might remain), I turned your function into the
> > following:
>
> Hmph! There seemingly is a problem however.
>
> I tried it on a few files, and it usually does it works quickly, or in
> no more than a few seconds. However, on one of my Org files, after many
> minutes, Emacs is still processing the command. If I interrupt it (with
> C-g), the main text displays its information, but the appendices do not.
>
> I do not know if this matters: while all the appendices together do not
> use much space in *this* file, they are merely made up of #+INCLUDE
> directives, each preceded by a short introductory text. The included
> files may be a bit longish however.
>
M-x toggle-debug-on-quit RET
Then when it gets into its rut and you interrupt with C-g, you'll get a
backtrace telling you where it was. If you repeat a couple of times and
you get the same backtrace each time, then you've probably found your
infinite looper.
Nick
next prev parent reply other threads:[~2012-02-27 6:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-26 2:42 Weight of headers François Pinard
2012-02-26 12:30 ` Nicolas Goaziou
2012-02-27 3:36 ` François Pinard
2012-02-27 3:56 ` François Pinard
2012-02-27 4:12 ` Nick Dokos [this message]
2012-02-27 4:52 ` Samuel Wales
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=25809.1330315951@alphaville \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=pinard@iro.umontreal.ca \
/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/org-mode.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).