emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: "Loyall, David" <david.loyall@nebraska.gov>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: We're doing it wrong. [WAS]: Zip utility on Windows for ODT exporter
Date: Wed, 27 Mar 2013 17:04:32 -0500	[thread overview]
Message-ID: <CA+M2ft_6d3ZYxBfnkEAy52NSH6vHk24-jqjeYRXC+v=yELycPA@mail.gmail.com> (raw)
In-Reply-To: <FCEE4469EE8B234199968ECA9B0661E208CD671A@STNEEX10MB02.stone.ne.gov>

On Wed, Mar 27, 2013 at 9:06 AM, Loyall, David
<david.loyall@nebraska.gov> wrote:
>> Just tried [...X] and don't have the [... utility] that Org is looking for.
>
> And that's why civilized programs don't depend on external executables from $PATH.
>
> Now, I'd imagine that some people have argued in the past that org shouldn't depend on external executables.  Clearly those arguments have failed.
>
> But, let's take a fresh look.  How about this rule of thumb: don't depend on external executables **from $PATH**.

That, and I'm not sure that "zip" was working on Windows anyway. I had
to edit ox-taskjuggler and change it to "zip.exe." Could be wrong, as
I ran into an issue where Wiz.exe from Info-zip gave an error when I
renamed it zip.exe and said it "couldn't find itself." Thus, I named
it back to Wiz.exe and created a hardlink to it called zip.exe. I
tried renaming to just 'zip' to satisfy Org, but then Windows doesn't
recognize it as an executable...

Thus, I resorted to editing ox-taskjuggler on Windows to do it's path
check on "zip.exe."

>
> Can we agree on that?
>
> How about: don't depend on external executables from $PATH, but allow the user to override via config.
>
> This is important on the 'reproducible research' front.
>

Agree -- let the user specify the path to the thing to use. Kind of like this:

#+begin_doc

org-ditaa-jar-path is a variable defined in `org-exp-blocks.el'.
Its value is
"~/.elisp/org.git/contrib/scripts/ditaa.jar"

Documentation:
Path to the ditaa jar executable.

#+end_doc

> Cheers,
> --Dave

Thanks for chiming in.


John

  reply	other threads:[~2013-03-27 22:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-27 14:06 We're doing it wrong. [WAS]: Zip utility on Windows for ODT exporter Loyall, David
2013-03-27 22:04 ` John Hendy [this message]
2013-04-06  0:10   ` Bastien
2013-04-06 17:56     ` John Hendy
2013-04-06 18:09       ` Bastien
2013-04-06 18:15         ` John Hendy
2013-04-06 18:19           ` Bastien
2013-04-06 20:54           ` Achim Gratz
2013-04-07  7:50 ` Achim Gratz
  -- strict thread matches above, loose matches on Subject: below --
2013-04-11 14:58 Loyall, David
2013-04-11 15:11 ` Bastien
2013-04-11 18:13 ` Achim Gratz

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='CA+M2ft_6d3ZYxBfnkEAy52NSH6vHk24-jqjeYRXC+v=yELycPA@mail.gmail.com' \
    --to=jw.hendy@gmail.com \
    --cc=david.loyall@nebraska.gov \
    --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).