emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Johan Ekh <ekh.johan@gmail.com>
To: Myles English <mylesenglish@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Use nomencl package with latex exporter?
Date: Mon, 6 Aug 2012 21:26:22 +0200	[thread overview]
Message-ID: <A2DC7E28-FE1E-45C8-92C6-FFD73F187651@gmail.com> (raw)
In-Reply-To: <87mx286wva.fsf@ed.ac.uk>

Thank you Myles,
I'm not that comfortable with cmake but I will give your solution a try and report My milage.

/ Johan

Sent from my iPad

On 6 aug 2012, at 14:14, Myles English <mylesenglish@gmail.com> wrote:

> 
> Johan Ekh writes:
> 
>> Hi all,
>> I use the default latex exporter in org-mode v7.8 to write documents using
>> a custom latex class which is built on "article".
>> I would like to use the "nomencl" latex package if possible.
> 
>> From the shell I usually run something like
>> 
>> makeindex filename.nlo -s nomencl.ist -o filename.nls
>> 
>> followed by latex or pdflatex, but how can I get the exporter to do
>> this?
> 
> I don't know the answer to your question, but when I came across the
> same problem, I used a makefile-like solution because I felt that the
> building process was becoming sufficiently complicated to warrant using
> a specialised tool.  If you are comfortable with CMake already it may be
> worth a look.  Have a look for "UseLatex.cmake".
> 
> Basically you get emacs to export the .tex file from the .org file:
> 
> add_custom_command(
>  OUTPUT ${CMAKE_CURRENT_BINARY_DIR}/mypaper.tex
>  COMMAND emacs --batch
>    --visit=${CMAKE_CURRENT_BINARY_DIR}/mypaper.org
>    --load=/home/me/myfuncs.el
>    --funcall org-export-as-latex-batch
>  DEPENDS orgfile
>  COMMENT "Exporting orgmode file to LaTeX using emacs"
>  )
> 
> And then bibtex and nomenclature are asked to do their stuff, and a pdf
> is produced, with something like this directive:
> 
> add_latex_document( mypaper.tex
>  INPUTS tex/bibliography.tex
>         texlib/mystyle.sty
>  BIBFILES texlib/mylibrary.bib
>  DEFAULT_PDF
>  USE_NOMENCL
> )
> 
> I also get it to generate all my R plots.  Other advantages are that you
> get an out-of-source build that is isolated (to some extent) in its own
> directory.  And I think it is easier to diagnose the problems when
> things go wrong, better than staring at an elisp backtrace.  Now if org
> would write my CMakeList.txt for me, that would be a fine thing.
> 
> Myles

  reply	other threads:[~2012-08-06 19:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-06  9:24 Use nomencl package with latex exporter? Johan Ekh
2012-08-06 12:14 ` Myles English
2012-08-06 19:26   ` Johan Ekh [this message]
2012-08-06 19:35     ` Nick Dokos
2012-08-08  6:40       ` Johan Ekh
2012-08-08  8:05         ` Andrew Young
2012-08-08 16:24         ` Nick Dokos

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=A2DC7E28-FE1E-45C8-92C6-FFD73F187651@gmail.com \
    --to=ekh.johan@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mylesenglish@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).