From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: [bug?, org-element] latex-environment delimiters must be at BOL
Date: Wed, 23 Jul 2014 10:29:54 +0200 [thread overview]
Message-ID: <87k374scjh.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <874my9ldz2.fsf@gmx.us> (rasmus@gmx.us's message of "Tue, 22 Jul 2014 15:28:33 +0200")
Hello,
Rasmus <rasmus@gmx.us> writes:
> Note that the maint/master version of org-element--current-element
> does not including a trailing "^".
That's becasue `org-element--current-element' always does the check at
the beginning of line.
> I'm not sure the location of stars matter much in a technical sense,
> though I have never come across any environments using stars other
> than for the last character.
>
> This document compiles fine, although it is an exercise is obscurity:
>
> \documentclass{minimal}
> \newenvironment{ab*cd}[1]{\bfseries{#1}}{}
> \newenvironment{*abcd}[1]{\bfseries{#1}}{}
> \begin{document}
> \begin{ab*cd} x \end{ab*cd}
> \begin{*abcd} x \end{*abcd}
> \end{document}
>
> I'm happy to accept only stars in the end, though.
I somehow was convinced that star characters were only allowed at the
end of the environment name. You're right, enforcing stars at the end is
unnecessary, and \\([A-Za-z0-9*]+\\) is better.
> Sorry, I can't push to Org-git. But a patch is attached.
I applied your patch with aforementioned change. Thank you.
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2014-07-23 8:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-10 11:54 [bug?, org-element] latex-environment delimiters must be at BOL Rasmus
2014-07-16 13:04 ` Nicolas Goaziou
2014-07-18 15:49 ` Rasmus
2014-07-20 17:49 ` Nicolas Goaziou
2014-07-21 9:29 ` Rasmus
2014-07-22 7:54 ` Nicolas Goaziou
2014-07-22 9:08 ` Rasmus
2014-07-22 10:03 ` Nicolas Goaziou
2014-07-22 13:28 ` Rasmus
2014-07-23 8:29 ` Nicolas Goaziou [this message]
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=87k374scjh.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
/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).