emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: suvayu ali <fatkasuvayu+linux@gmail.com>
To: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Source blocks for tiny snippets
Date: Sat, 22 Oct 2011 03:10:26 +0200	[thread overview]
Message-ID: <CAMXnza20QnGRA22a8Mmgx_j_jW6NGAiCzAmGzhY7276qgabAiw@mail.gmail.com> (raw)

Hi everyone,

I was wondering what people do when they need to put a few (1 or 2)
lines of code snippets in org files? I like the syntax highlighting one
gets in an org buffer and in HTML export with code blocks. Is there some
work around other than have code blocks for every line I want to

As an example consider this paragraph:

Edit job options for number of events and other configurations
: $ $EDITOR $GAUSSOPTS/<options_files>.py
The number of events in a job can be customised with the option
: LHCbApp().EvtMax = nEvts
To run the generator only, set the property below.
: Gauss().Phases = ["Generator"]
To turn on full monitoring and dump an ntuple to a root file, include
the opts files as below. It can be customised further to suit the needs.
: importOptions('$GAUSSOPTS/<some>.opts')

In the above example you have a mix of bash and python snippets.

Any thought?


Open source is the future. It sets us free.

             reply	other threads:[~2011-10-22  1:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-22  1:10 suvayu ali [this message]
2011-10-22 16:08 ` Source blocks for tiny snippets Eric Schulte
2011-10-24  9:58   ` suvayu ali
2011-10-24 10:06   ` Thorsten
2011-10-24 14:02     ` Nick Dokos
2011-10-24 16:35       ` Thorsten
2011-10-25  1:44       ` 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:

  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=CAMXnza20QnGRA22a8Mmgx_j_jW6NGAiCzAmGzhY7276qgabAiw@mail.gmail.com \
    --to=fatkasuvayu+linux@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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