From: "Eli Zaretskii" <eliz@is.elta.co.il>
Cc: emacs-devel@gnu.org
Subject: Re: locate-file in Emacs
Date: Wed, 17 Apr 2002 08:47:53 +0300 [thread overview]
Message-ID: <379-Wed17Apr2002084752+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <sxshemahq3t.fsf@florida.arsdigita.de> (message from Hrvoje Niksic on Wed, 17 Apr 2002 07:05:26 +0200)
> From: Hrvoje Niksic <hniksic@arsdigita.com>
> Date: Wed, 17 Apr 2002 07:05:26 +0200
>
> For example, to find an elisp file in load-path, one would use this:
>
> (locate-file "simple" load-path '(".elc" ".el"))
> => "/usr/local/lib/xemacs-21.4.6/lisp/simple.elc"
>
> Or, to locate a Unix executable:
>
> (locate-file "ls" (split-string (getenv "PATH") path-separator)
> nil 'executable)
> => "/bin/ls"
>
> To make the same code work under Windows:
>
> (locate-file "links" (split-string (getenv "PATH") path-separator)
> '("" ".exe") 'executable)
> => "/usr/bin/links"
>
> I find that there are many uses for this kind of lookup across a list
> of directories, and I would like to be able to use this function in
> portable elisp programs. The XEmacs version is written in C with
> (probably) unclear copyright status, but Richard agreed to include a
> Lisp version of the function. I came back to that yesterday and wrote
> one.
>
> The code follows below. Please let me know what you think.
I'm not saying that we already have this functionality (I didn't
check that), but I thought I'd mention similar functionality:
- executable-find in executable.el
- find-lisp.el
- the openp function (implemented in C) which can be used as a base
for either a C primitive or a Lisp function (it is currently used
by `load').
I do agree that the feature you suggest is a useful one.
next prev parent reply other threads:[~2002-04-17 5:47 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-17 5:05 locate-file in Emacs Hrvoje Niksic
2002-04-17 5:47 ` Eli Zaretskii [this message]
2002-04-17 8:53 ` Hrvoje Niksic
2002-04-17 9:28 ` Stefan Monnier
2002-04-17 9:47 ` Hrvoje Niksic
2002-04-17 10:01 ` Stefan Monnier
2002-04-18 13:16 ` Hrvoje Niksic
2002-04-18 13:54 ` Miles Bader
2002-04-18 14:09 ` Hrvoje Niksic
2002-04-18 14:25 ` Miles Bader
2002-04-18 14:08 ` Stefan Monnier
2002-04-18 15:11 ` Hrvoje Niksic
2002-04-18 15:27 ` Stefan Monnier
2002-04-18 16:20 ` Hrvoje Niksic
2002-04-18 18:59 ` Stefan Monnier
2002-04-25 12:12 ` Hrvoje Niksic
2002-04-25 22:52 ` Stefan Monnier
2002-05-06 15:58 ` Hrvoje Niksic
[not found] ` <200205061655.g46Gt3K01382@rum.cs.yale.edu>
2002-05-06 19:53 ` Hrvoje Niksic
[not found] ` <200205062052.g46KqwO02482@rum.cs.yale.edu>
2002-05-06 20:59 ` Hrvoje Niksic
2002-05-06 21:12 ` Stefan Monnier
2002-05-06 21:57 ` Hrvoje Niksic
2002-05-07 20:06 ` Richard Stallman
2002-04-18 16:39 ` Eli Zaretskii
2002-04-18 16:24 ` Hrvoje Niksic
2002-04-19 5:25 ` Richard Stallman
2002-04-18 15:31 ` Miles Bader
2002-04-18 16:29 ` Hrvoje Niksic
2002-04-18 16:45 ` Miles Bader
2002-04-18 16:49 ` Hrvoje Niksic
2002-04-18 16:54 ` Miles Bader
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=379-Wed17Apr2002084752+0300-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=emacs-devel@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.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).