From: Eric Schulte <schulte.eric@gmail.com>
To: suvayu ali <fatkasuvayu+linux@gmail.com>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Source blocks for tiny snippets
Date: Sat, 22 Oct 2011 10:08:36 -0600 [thread overview]
Message-ID: <87zkgtypob.fsf@gmail.com> (raw)
In-Reply-To: <CAMXnza20QnGRA22a8Mmgx_j_jW6NGAiCzAmGzhY7276qgabAiw@mail.gmail.com> (suvayu ali's message of "Sat, 22 Oct 2011 03:10:26 +0200")
suvayu ali <fatkasuvayu+linux@gmail.com> writes:
> 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
> include?
>
> 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.
>
Currently there is no more concise way to specify code blocks other than
the normal code block format. Although it doesn't currently exist maybe
an option could be added to hide the #+BEGIN/END_SRC lines so that they
don't appear in the buffer. That combined with a helper for specifying
code blocks (I use yasnippets for this) should serve.
Best -- Eric
--
Eric Schulte
http://cs.unm.edu/~eschulte/
next prev parent reply other threads:[~2011-10-22 16:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-22 1:10 Source blocks for tiny snippets suvayu ali
2011-10-22 16:08 ` Eric Schulte [this message]
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:
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=87zkgtypob.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=fatkasuvayu+linux@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).