From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: "Charles C. Berry" <ccberry@ucsd.edu>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Stack overflow in regexp matcher
Date: Fri, 28 Nov 2014 19:33:53 +0100 [thread overview]
Message-ID: <m2h9xjcgz2.fsf@charm-wifi.irisa.fr> (raw)
In-Reply-To: <alpine.OSX.2.00.1410251127240.792@charles-berrys-macbook.local> (Charles C. Berry's message of "Sat, 25 Oct 2014 11:34:32 -0700")
[-- Attachment #1: Type: text/plain, Size: 910 bytes --]
On 2014-10-25 12:34, "Charles C. Berry" <ccberry@ucsd.edu> writes:
> Further, changing that regexp to
>
> "^[^%\n]*\\\\usepackage.*{biblatex}"
>
> and byte-compiling reftex-parse.el.gz seems to make the problem go away.
The auctex developers have fixed the issue, which will be available in
the next version of emacs (since reftex is bundled).
In the meantime, they suggested to add the following in a configuration
file:
#+begin_src emacs-lisp
(with-eval-after-load 'reftex-parse
(defun reftex-using-biblatex-p ()
"Return non-nil if we are using biblatex rather than bibtex."
(if (boundp 'TeX-active-styles)
;; the sophisticated AUCTeX way
(member "biblatex" TeX-active-styles)
;; poor-man's check...
(save-excursion
(re-search-forward "^[^%\n]*?\\\\usepackage.*{biblatex}" nil t)))))
#+end_src
Best,
Alan
--
OpenPGP Key ID : 040D0A3B4ED2E5C7
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 494 bytes --]
next prev parent reply other threads:[~2014-11-28 18:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 6:41 Stack overflow in regexp matcher Alan Schmitt
2014-10-24 19:02 ` Charles Berry
2014-10-24 19:51 ` Gregor Zattler
2014-10-25 17:00 ` Charles C. Berry
2014-10-25 18:34 ` Charles C. Berry
2014-11-28 18:33 ` Alan Schmitt [this message]
2014-10-26 11:11 ` Alan Schmitt
2014-10-25 9:24 ` Alan Schmitt
-- strict thread matches above, loose matches on Subject: below --
2010-11-20 16:03 Michael Brand
2010-11-28 20:08 ` Matt Lundin
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=m2h9xjcgz2.fsf@charm-wifi.irisa.fr \
--to=alan.schmitt@polytechnique.org \
--cc=ccberry@ucsd.edu \
--cc=emacs-orgmode@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 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).