unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Aaron Jensen <aaronjensen@gmail.com>
Cc: 26586@debbugs.gnu.org
Subject: bug#26586: 25.1; header-line-format spins cpu
Date: Fri, 21 Apr 2017 17:51:25 +0300	[thread overview]
Message-ID: <83efwlak5u.fsf@gnu.org> (raw)
In-Reply-To: <CAHyO48wQaHQ=zHybvnfgWLaZQuMtULStRAUmDrxqX0ewAOyfcQ@mail.gmail.com> (message from Aaron Jensen on Fri, 21 Apr 2017 07:29:00 -0700)

> From: Aaron Jensen <aaronjensen@gmail.com>
> Date: Fri, 21 Apr 2017 07:29:00 -0700
> Cc: 26586-done@debbugs.gnu.org
> 
> The code generating it was org-sticky-header
> https://github.com/alphapapa/org-sticky-header/blob/master/org-sticky-header.el
> 
> I was investigating and infinite loop reported here:
> 
> https://github.com/alphapapa/org-sticky-header/issues/4
> 
> The org file that triggers the bug is:
> 
> * [[elisp:(org-projectile:open-project%20"foobar")][xxxxxxxxxx]]
> 
> which is generated by org-projectile

Thanks for the info.

> So, I'm guessing that org-sticky-header needs to escape or remove
> elisp links before turning org headlines into a header?

Yes, definitely.





  reply	other threads:[~2017-04-21 14:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-21  6:17 bug#26586: 25.1; header-line-format spins cpu Aaron Jensen
2017-04-21  8:07 ` Eli Zaretskii
2017-04-21  8:15 ` Eli Zaretskii
2017-04-21 14:29   ` Aaron Jensen
2017-04-21 14:51     ` Eli Zaretskii [this message]
2017-04-21 15:34       ` Aaron Jensen
2017-04-21 17:31         ` Eli Zaretskii
2017-04-21 18:01           ` Aaron Jensen
2017-04-21 18:32             ` Andreas Schwab
2017-04-22 14:40               ` Aaron Jensen
2017-04-22 14:50                 ` Eli Zaretskii
2017-04-22 15:11                   ` Aaron Jensen
2017-04-21 18:47             ` Eli Zaretskii
2017-04-21 19:04               ` Aaron Jensen

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=83efwlak5u.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=26586@debbugs.gnu.org \
    --cc=aaronjensen@gmail.com \
    /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).