emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: org-program-exists vs executable-find
Date: Fri, 20 Apr 2012 22:24:59 +0200	[thread overview]
Message-ID: <80ehrinobo.fsf@somewhere.org> (raw)
In-Reply-To: 87mx66zlz1.fsf@altern.org

Hi Bastien,

Bastien wrote:
> "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>
>>> The name `org-program-exists' is actually misleading, it should be
>>> `org-executable-call' instead, while still checking if the executable
>>> exists before calling it.
>>
>> Nope, the name is not misleading. The documentation string is false -- what
>> I hadn't noticed, btw.
>>
>> That function just checks if the executable can be found; it does _not_
>> call it afterward.
>
> You're right, I just fixed the docstring.
>
>> On Linux and Mac OS, it just calls "which + <program name>", no more... On
>> Windows, it simply fails immediately (even if the program could be found).
>
> If there is an equivalent of `which' on windows let me know,

Not that I know, reason why I (must) have Cygwin...

> we can generalize this function.

Why not replacing it simply by `executable-find': I don't see what it adds to
it?  I would not say so if it was some upper abstraction, but I do feel
they're simply the same.

If not, the opposite should be done: replacing the 10 calls to
`executable-find' by calls to `org-program-exists'...

Best regards,
  Seb

-- 
Sebastien Vauban

  reply	other threads:[~2012-04-20 20:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-18 12:46 org-program-exists vs executable-find Sebastien Vauban
2012-04-18 13:25 ` Bastien
2012-04-18 14:39   ` Sebastien Vauban
2012-04-20 11:22     ` Bastien
2012-04-20 20:24       ` Sebastien Vauban [this message]
2012-04-20 20:42         ` Martyn Jago
2012-04-21 10:13         ` Achim Gratz
2012-04-28 21:44         ` Bastien
2012-06-14 13:05         ` 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=80ehrinobo.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).