From: Scot Becker <scot.becker@gmail.com>
To: nicholas.dokos@hp.com
Cc: tassilo@member.fsf.org, emacs-orgmode@gnu.org, gerald.jean@dgag.ca
Subject: Re: RE Re: Issues with org-mode and LaTeX export.
Date: Fri, 22 Oct 2010 19:03:50 +0100 [thread overview]
Message-ID: <AANLkTikUafq4zSuvtPrukbD7XYHn-pO9STwuTo0_BQhg@mail.gmail.com> (raw)
In-Reply-To: <9716.1287690471@alphaville.usa.hp.com>
[-- Attachment #1.1: Type: text/plain, Size: 3656 bytes --]
I do hear you about not wanting to add maintenance overhead to yourself, but
when they install the new Emacs, you even then may find you need a more
recent recent org-mode release in your home directory. It does come with
Emacs, to be sure, but they've been quite conservative about their cutoff
dates, so even a brand new Emacs version typically has an org-mode version
which has been significantly improved upon.
sb
On Thu, Oct 21, 2010 at 8:47 PM, Nick Dokos <nicholas.dokos@hp.com> wrote:
> gerald.jean@dgag.ca wrote:
>
> > I tried this:
> >
> > #+LATEX_HEADER: "\usepackage{longtable}"
> >
> > No effects?
> >
>
> AFAIK, the quotes are not necessary, but the reason it's not
> working is indeed that your version of org-mode doesn't know about
> LATEX_HEADER at all.
>
> It was implemented with this commit:
>
> commit 20364d043a51c3c71493369c58a43b49566dbdaa
> Author: Carsten Dominik <carsten.dominik@gmail.com>
> Date: Thu Oct 2 15:00:14 2008 +0200
>
> Implement #+LATEX_HEADER special.
>
> Proposed by Austin Frank and apparently also by Russel Adams.
>
>
> which I believe appeared in
>
> release_6.08
>
> Note that the commit is two years old.
>
> > >
> > > > I also looked at the manual to selectively export a part of the org
> > > > file. They talk about the "org-export-select-tags" and
> > > > "org-export-exclude-tags"; these variables don't even exist?
> > >
> > > They do. Are you still using that old org version 5.x? If so, well,
> > > then maybe there were no such variables. And somewhen in org version
> > > 6.x the export facilities were completely rewritten, so I guess you are
> > > pretty alone with your problems unless you get a recent version.
> >
> > For the time being I am stuck with this version. I am sending a request
> to
> > our IT group to upgrade Emacs to the most recent version for the version
> of
> > RedHat we have, this should have a more recent version of org-mode, if I
> am
> > lucky that should be done in a couple weeks. In the mean time I will
> > manually add, or exclude, what I want from the exported "*.tex" file.
> >
>
> A couple of weeks?!? And you are not even sure which version of emacs
> and org-mode you are going to get? I'd say, build your own: get
> emacs/orgmode from the git mirror and build it yourself, install it in
> your home directory if necessary. Even if it takes you a week or two to
> get it done, at the end of it you'll be much better off at the end of
> it.
>
> If you have a community of users, this might be more difficult, but maybe
> you can exercise concerted pressure on your IT dept: they might be more
> willing to listen to ten people than to one.
>
> If you are reasonably comfortable with git and make, it should only take
> an hour or so to update/build/install; and assuming you stay with
> "released" versions, you will only have to do that every couple of
> months.
>
> In addition, depending on what emacs version you have, you might be able
> to run recent org-mode even if your emas is old (certainly on emacs 23,
> probably on emacs 22, and just maybe on emacs 21, although I'm not sure
> about these). That might be enough for your purposes and it reduces
> time requirements to just a few minutes every month or two.
>
> FWIW, the only use I have of whatever emacs gets installed with a system
> is to bootstrap the latest emacs/orgmode: after that, it's deleted (or
> at least, never used again).
>
> Nick
>
>
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
[-- Attachment #1.2: Type: text/html, Size: 4747 bytes --]
[-- Attachment #2: Type: text/plain, Size: 201 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2010-10-22 18:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 14:42 Issues with org-mode and LaTeX export gerald.jean
2010-10-21 15:03 ` Tassilo Horn
2010-10-21 16:56 ` RE " gerald.jean
2010-10-21 17:42 ` Tassilo Horn
2010-10-21 17:58 ` gerald.jean
2010-10-21 18:26 ` Erik Iverson
2010-10-21 18:37 ` gerald.jean
2010-10-21 19:47 ` Nick Dokos
2010-10-22 18:03 ` Scot Becker [this message]
2010-10-21 17:47 ` Thomas S. Dye
2010-10-21 15:10 ` Giovanni Ridolfi
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=AANLkTikUafq4zSuvtPrukbD7XYHn-pO9STwuTo0_BQhg@mail.gmail.com \
--to=scot.becker@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=gerald.jean@dgag.ca \
--cc=nicholas.dokos@hp.com \
--cc=tassilo@member.fsf.org \
/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).