emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Eric Schulte" <schulte.eric@gmail.com>
To: Rainer M Krug <r.m.krug@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Inline source block documentation
Date: Wed, 08 Sep 2010 14:30:05 -0600	[thread overview]
Message-ID: <87eid4kmgi.fsf@gmail.com> (raw)
In-Reply-To: <4C87DCE4.8030200@gmail.com> (Rainer M. Krug's message of "Wed, 08 Sep 2010 20:58:44 +0200")

Done, thanks -- Eric

Rainer M Krug <r.m.krug@gmail.com> writes:

> On 08/09/10 20:27, Eric Schulte wrote:
>> Hi Rainer,
>> 
>> Thanks for pointing this out.  I've just added inline syntax to the
>> _Structure of code blocks_ section of the manual.
>> 
>> This may not be sufficient, but it should be an improvement.
>
> Definitely - and I think it should be fine. But I would suggest to use
> the term "inline source block" here as well, as then one can find it
> when searching the pdf.
> e.g:
>
>
> code blocks can also be embedded in text as so called inline code blocks as
>
> Cheers,
>
> Rainer
>
>
>> 
>> Best -- Eric
>> 
>> Rainer M Krug <r.m.krug@gmail.com> writes:
>> 
>>> Hi
>>>
>>> I was struggling with inline source blocks, because I did not find them
>>> in the documentation - they only occur under "Code block specific header
>>> arguments":
>>>
>>> ###QUOTE BEGIN
>>> Similarly, it is possible to set header arguments for inline code blocks:
>>> src_haskell[:exports both]{fac 5}
>>> ###QUOTE END
>>>
>>> Did I miss them? If not, could they be included?
>>>
>>> Thanks,
>>>
>>> Rainer

      reply	other threads:[~2010-09-08 20:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-08  9:15 Inline source block documentation Rainer M Krug
2010-09-08 18:27 ` Eric Schulte
2010-09-08 18:58   ` Rainer M Krug
2010-09-08 20:30     ` Eric Schulte [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=87eid4kmgi.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=r.m.krug@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).