emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: odt exporter on mixed org setup
Date: Thu, 23 Jan 2014 18:22:41 +0100	[thread overview]
Message-ID: <87ob32ehpa.fsf@Rainer.invalid> (raw)
In-Reply-To: 877g9rqlv0.fsf@gmail.com

Jambunathan K writes:
> I have my reservations.  With stock Emacs Snapshot (i.e., without any
> separate Org installation - git or elpa) at Bzr version 116124, at line
> 16, I am seeing
>
>     ;;;###autoload
>     (defvar org-odt-data-dir "/usr/share/emacs/etc/org"
>       "The location of ODT styles.")
>
> I hard-coded path, on a platform-independent file, makes me cringe?

That's the result of using Emacs' build system, not Org's.  I was only
talking about the latter and if you configure it as recommended on Worg
for the various platforms then installing Org will set this up
correctly.  If you find it does not, then that's a bug I'll try to fix.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra

  reply	other threads:[~2014-01-23 17:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-16  5:47 odt exporter on mixed org setup Rustom Mody
2014-01-16  7:53 ` Andreas Leha
2014-01-16  8:29 ` Jambunathan K
2014-01-16 11:29   ` Rustom Mody
2014-01-16 14:48     ` Jambunathan K
2014-01-16 16:38       ` Achim Gratz
2014-01-23  5:59         ` Jambunathan K
2014-01-23 17:22           ` Achim Gratz [this message]
2014-01-23 17:31             ` Jambunathan K
2014-01-16 14:52     ` Jambunathan K
2014-01-16 17:20       ` Rustom Mody
2014-01-18 18:53         ` Jambunathan K
2014-01-19  3:27           ` Rustom Mody
2014-01-19  4:10             ` Rustom Mody
2014-01-19  4:20               ` Jambunathan K
2014-01-19  4:29               ` Jambunathan K
2014-01-16 16:29     ` Achim Gratz
2014-01-16 11:30 ` Miguel Ruiz

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=87ob32ehpa.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=emacs-orgmode@gnu.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).