emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: Re: [babel][patch] BUG in inline source blocks
Date: Fri, 27 Jan 2012 23:26:26 +0100	[thread overview]
Message-ID: <87y5ss6aul.fsf@med.uni-goettingen.de> (raw)
In-Reply-To: m2ty3i1bo6.fsf@btinternet.com

Martyn Jago <martyn.jago@btinternet.com> writes:

> Martyn Jago <martyn.jago@btinternet.com> writes:
>
>> Hi,
>>
>> Andreas Leha <andreas.leha@med.uni-goettingen.de> writes:
>>
>>> Hi all,
>>>
>>> I experience unexpected behaviour when an inline source block is not
>>> preceded by whitespace.
>>>
>>> Example:
>>> =======================
>>> * Test inline
>>>   This is a functional inline src_R{print("source block")}.
>>>
>>>   This (src_R{print("here")}) is not.
>>> =======================
>>>
>>> Regards,
>>> Andreas 
>>
>> I can confirm this behaviour and provide a patch to allow for inline
>> source blocks to be preceded by punctuation, or, for instance, enclosed
>> in parenthesis, as in Andreas' example. Patch is attached for
>> consideration.
>>
>> Best, Martyn
>
> This is an updated version of the previous patch, with debug noise
> removed, and a couple of extra tests.
>
> Best, Martyn

Hi Martyn,

thanks for this patch!  It does half the job for me.  Now export (or
evaluation) already work.  But in the export I get a space inserted.

I my example, I'd expect "(here)" to appear in the export, but I get "( here)".

Best,
Andreas

next prev parent reply	other threads:[~2012-01-27 22:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-26  7:36 [babel] BUG in inline source blocks Andreas Leha
2012-01-26 13:29 ` [babel][patch] " Martyn Jago
2012-01-26 19:55   ` Martyn Jago
2012-01-27 22:26     ` Andreas Leha [this message]
2012-01-27 23:33       ` Eric Schulte
2012-01-28  9:28         ` Andreas Leha
2012-01-29  0:34           ` Martyn Jago
2012-01-30 16:06             ` Eric Schulte

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=87y5ss6aul.fsf@med.uni-goettingen.de \
    --to=andreas.leha@med.uni-goettingen.de \
    --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

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).