emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Andrey Smirnov <andrew.smirnov@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [org-babel] [PATCH] Improve ditta.jar finding heuristics
Date: Mon, 21 Nov 2011 12:16:08 +0700	[thread overview]
Message-ID: <87pqgmt5rb.fsf@gmail.com> (raw)
In-Reply-To: <874nxywwpy.fsf@gmail.com> (Eric Schulte's message of "Sun, 20 Nov 2011 09:35:14 -0700")

Eric Schulte <schulte.eric@gmail.com> writes:

> Hi Andrey,
>
> The variable `org-ditaa-jar-path' can be used to specify a non-standard
> location for the ditaa jar file.

True, but my patch is not about doing away with `org-ditaa-jar-path'
variable, it is about broadening the definition of "standard location"
so to speak.

Right now, being defined relatively to ob-ditaa.el, aforementioned
standard location is at the mercy of what/whoever that is responsible
for deciding where all the stuff belonging to emacs and org-mode goes.

IMHO, that floating filesystem location is hardly more standard than the
place where Distro X's package management tools place ditta.jar
after installation.
         
> Org-mode has *many* customization
> variables, and for most problems a variable will exist to solve the
> problem, 

I understand where you're coming from. True, it is not possible to
handle all obscure and arcane cases, that's what all these variables are
for, but I don't think that a situation where user installs ditaa and
later emacs, both via the package management system and find themselves
unable to draw awesome ditaa diagrams without looking a variable up in
documentation, adding appropriate code to his configuration file and
hitting C-x C-e is some sort of a fringe use-case. If only
myself and maybe another person has ever hit that roadblock, than I
agree, it is not worth adding any additional code, and I rest my case.

> the `apropos' command can be very useful for finding these
> variables.
>

Thanks for the tip, didn't know about that particular command.
I usually use combination of C-h v and good old
M-x download-the-source-and-look-how-the-thing-works :-).

Andrey Smirnov

  reply	other threads:[~2011-11-21  5:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-20 13:37 [org-babel] [PATCH] Improve ditta.jar finding heuristics Andrey Smirnov
2011-11-20 16:35 ` Eric Schulte
2011-11-21  5:16   ` Andrey Smirnov [this message]
2011-11-21 18:02     ` Eric Schulte
2011-12-11  3:12 ` Andrey Smirnov
2011-12-11  5: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=87pqgmt5rb.fsf@gmail.com \
    --to=andrew.smirnov@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=schulte.eric@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).