emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Thomas S. Dye" <tsd@tsdye.com>
To: rpgoldman@sift.info
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Request for suggestions including source code
Date: Wed, 4 May 2011 12:23:53 -1000	[thread overview]
Message-ID: <CEDB3DD2-47B5-4C29-9B71-85C50C56BBEA@tsdye.com> (raw)
In-Reply-To: <4DC1CC32.4090003@sift.info>


On May 4, 2011, at 11:59 AM, Robert Goldman wrote:

> On 5/4/11 May 4 -4:13 PM, Thomas S. Dye wrote:
>> Aloha Robert,
>>
>> Have a look at the listings and minted packages.  You can specify  
>> font
>> size on a per-document or per-language basis.  I believe listings  
>> has an
>> option to wrap long lines (don't remember this for minted, though).
>>
>> The instructions here might be helpful:
>>
>> http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-12_2
>
> Hm.  I'm still grappling with this.  I am including many of these
> examples by using a source snippet (in sh) that goes out and pulls the
> example out of a source code file.
>
> Even after adding
>
> #+LaTeX_HEADER \usepackage{listings}
>
> and
>
> #+src: setup-listings
>

Sorry for the confusion.  In the example, the line

#+source: setup-listings

names the source code block that follows.   I don't think it will do  
anything by itself in your document.

That code block named setup-listings contains an example of a listings  
setup that maps Org-mode's output for Emacs Lisp code blocks to  
something listings recognizes.  It can be executed in Org-mode, using  
Babel, to setup the listings export.  After this is done, then the  
example should export correctly.

I'm not sure what is going wrong on your end.  Perhaps org-export- 
latex-custom-lang-environments needs to be configured for the language  
you're using?

hth,
Tom

> to the top of my file, and setting
>
> org-export-latex-listings to 'listings
>
> the :results of the source blocks, which look like, e.g., the  
> following:
>
> #+begin_src sh :exports results :results output
> sourceSample.perl single code/ontology/top.prxo 'Class Pattern'
> #+end_src
>
> come out wrapped in
>
> \begin{verbatim}
> ...
> \end{verbatim}
>
> Maybe I'm not doing enough.  I'm a bit confused by the listings  
> example
> in the tutorial because it has the configuration examples be in their
> own source block, and adds all of the options for specially  
> typesetting
> particular programming languages.  It's not altogether clear to me  
> which
> bits of that are critical to getting the listings stuff to work at  
> all,
> and which are only specially tailoring its function.
>
> Is it necessary to specify what programming language is used in  
> order to
> typeset using listings?  I am using a domain specific language for  
> which
> there is no obvious listings setting and, anyway, what I am trying to
> typeset is the /results/ of the source blocks, which are in a  
> different
> programming language from the /source/ of the source blocks.
>
> I suspect I am just looking for a simpler solution, e.g., one which
> would make org-mode give me the source blocks in
>
> {\small
> \begin{verbatim}
> ...
> \end{verbatim}
> }
>
> instead of
>
> \begin{verbatim}
> ...
> \end{verbatim}
>
> or something like that.
>
> best,
> r
>
>

  reply	other threads:[~2011-05-04 22:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-04 20:53 Request for suggestions including source code Robert Goldman
2011-05-04 21:13 ` Thomas S. Dye
2011-05-04 21:44   ` Nick Dokos
2011-05-04 22:01     ` Robert Goldman
2011-05-04 23:10       ` Nick Dokos
2011-05-05  0:11         ` Robert Goldman
2011-05-04 21:59   ` Robert Goldman
2011-05-04 22:23     ` Thomas S. Dye [this message]
2011-05-04 22:29       ` Robert Goldman
2011-05-04 22:49         ` brian powell
2011-05-05 17:07         ` 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=CEDB3DD2-47B5-4C29-9B71-85C50C56BBEA@tsdye.com \
    --to=tsd@tsdye.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=rpgoldman@sift.info \
    /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).