From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 25425@debbugs.gnu.org
Subject: bug#25425: cannot express search path
Date: Sun, 22 Jan 2017 22:56:29 +0100 [thread overview]
Message-ID: <87d1feep2q.fsf@gnu.org> (raw)
In-Reply-To: <87lgug72vc.fsf@elephly.net> (Ricardo Wurmus's message of "Thu, 12 Jan 2017 15:46:15 +0100")
Hello!
Ricardo Wurmus <rekado@elephly.net> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> I think this should work:
>>
>> (search-path-specification
>> (variable "LUA_PATH")
>> (separator ";")
>> (files '("share/lua/5.3"))
>> (file-pattern "\\.lua$")
>> (file-type 'regular))
>
> I tried this very same thing but it doesn’t work because Lua expects
> placeholders (“?”) in the search paths. The placeholders are replaced
> with the actual package names. If the actual file name does not exist
> it will try the next pattern. If the file *does* exist – which *will* be
> the case for any of the files on LUA_PATH that have been generated by
> the search-path-specification — Lua will try to load the package from
> that path.
>
> This will fail because a search for the “lpeg” module would be satisfied
> by the file “re.lua”, because that’s the first valid file on the
> LUA_PATH. “re.lua” requires “lpeg” itself, so another lookup is
> performed, which will again result in “re.lua” to be loaded…
>
> AIUI we must generate a value for LUA_PATH that keeps the placeholders
> intact.
So are you saying that it’s important for the question marks to remain
intact?
This sounds terrible. I’m not sure how to address it, and I don’t feel
like stretching the search path mechanism this much.
Thoughts?
Ludo’.
next prev parent reply other threads:[~2017-01-22 21:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 10:57 bug#25425: lua does not set search paths Ricardo Wurmus
2017-01-12 12:19 ` bug#25425: cannot express search path Ricardo Wurmus
2017-01-12 14:38 ` Ludovic Courtès
2017-01-12 14:46 ` Ricardo Wurmus
2017-01-22 21:56 ` Ludovic Courtès [this message]
2017-01-22 22:34 ` Ricardo Wurmus
2021-03-24 22:27 ` zimoun
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d1feep2q.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=25425@debbugs.gnu.org \
--cc=rekado@elephly.net \
/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/guix.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).