From: Eric Schulte <eric.schulte@gmx.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org, cberry@tajo.ucsd.edu,
Eric Schulte <eric.schulte@gmx.com>
Subject: Re: [New Latex Exporter][BABEL][BUG] lists and inline src
Date: Thu, 20 Sep 2012 11:26:00 -0600 [thread overview]
Message-ID: <87sjac38t3.fsf@gmx.com> (raw)
In-Reply-To: <87392ctygj.fsf@gmail.com> (Nicolas Goaziou's message of "Thu, 20 Sep 2012 19:07:24 +0200")
Nicolas Goaziou <n.goaziou@gmail.com> writes:
> Hello,
>
> Eric Schulte <eric.schulte@gmx.com> writes:
>
>> Thanks for finding the source of this problem. The preceding character
>> is checked so that inline source blocks can be commented. E.g., a user
>> may want =src_sh{date}= to appear verbatim.
>
> =src_sh{date}= won't be expanded by `org-babel-exp-non-block-elements'
> (is there another function executing them?) since the current version
> checks object at point (in this case, it is a verbatim object, not an
> inline-src-block). So, in this case, there's no need for the check.
>
>> Similarly if the preceding character is a letter e.g.,
>> notsrc_sh{date}, then the source block should not be executed.
>
> I don't understand why it wouldn't be expanded in that situation. It can
> be useful if results are raw: it becomes a beefed-up macro.
>
>> Ideally there would be a way to specify that *if* a character exists
>> before the code block it must have some property, or to match the
>> beginning of the element as another regexp option. I would say we can
>> go ahead and remove the leading portion of the regexp, but as I recall I
>> wrote it in response to legitimate complaints on the mailing list about
>> the overly permissive behavior of inline source blocks, and I do not
>> want for those problems to re-emerge.
>
> I understand, but it looks like a very drastic solution. It may be worth
> reconsidering it for 8.x branch. If problems re-emerge then, test cases
> will be provided. What do you think about it?
>
> For 7.9.x, I'll just commit the workaround.
>
Yea, that sounds reasonable, thanks for taking care of this. If I find
time I'll dig through the mailing list and see if I can find the exact
reason why that portion of the regexp was added.
I've had the experience before of reverting a piece of code that seemed
superfluous to then have old bugs re-emerge and finally revert my
reversion. So I now try to err on the side of deference towards
existing code.
Cheers,
>
>
> Regards,
--
Eric Schulte
http://cs.unm.edu/~eschulte
next prev parent reply other threads:[~2012-09-20 17:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-18 21:48 [BABEL][BUG] lists and inline src cberry
2012-09-19 7:31 ` Bastien
2012-09-19 15:45 ` cberry
2012-09-19 23:50 ` [New Latex Exporter][BABEL][BUG] " Eric Schulte
2012-09-20 12:13 ` Nicolas Goaziou
2012-09-20 14:28 ` Eric Schulte
2012-09-20 17:07 ` Nicolas Goaziou
2012-09-20 17:26 ` Eric Schulte [this message]
2012-09-20 19:27 ` Nicolas Goaziou
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=87sjac38t3.fsf@gmx.com \
--to=eric.schulte@gmx.com \
--cc=cberry@tajo.ucsd.edu \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@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/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).