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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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


- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Natural Sciences Building
Office Suite 2039
Stellenbosch University
Main Campus, Merriman Avenue
Stellenbosch
South Africa

Tel:        +33 - (0)9 53 10 27 44
Cell:       +27 - (0)8 39 47 90 42
Fax (SA):   +27 - (0)8 65 16 27 82
Fax (D) :   +49 - (0)3 21 21 25 22 44
Fax (FR):   +33 - (0)9 58 10 27 44
email:      Rainer@krugs.de

Skype:      RMkrug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkyH3OQACgkQoYgNqgF2egotjACfeASzAMK9KKPtoSHJkGiy7O5A
lUAAn3bOBpJvdyyg+xv/ohqB2gSV65ua
=UoB+
-----END PGP SIGNATURE-----

  reply	other threads:[~2010-09-08 18:58 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 [this message]
2010-09-08 20:30     ` 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=4C87DCE4.8030200@gmail.com \
    --to=r.m.krug@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=schulte.eric@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).