From: dana <dana@dana.is>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: [PATCH] Completion: Add _lua
Date: Mon, 23 Jul 2018 06:40:04 -0500 [thread overview]
Message-ID: <E01C10CC-1034-4DCE-BC93-9CBAD099703A@dana.is> (raw)
In-Reply-To: <84B28497-6E79-439D-BFB5-CDD32D6BECB5@dana.is>
On 23 Jul 2018, at 01:50, dana <dana@dana.is> wrote:
>_lua_libraries is maybe a little excessive, tbh, but i found it useful — i don't
>think there's any 'official' way to do what it does.
Eric showed me his own _lua function, which uses an embarrassingly less silly
method of building the library matches for this. His also handles script
arguments more like other interpreters' functions do. I've incorporated those
enhancements here.
dana
diff --git a/Completion/Unix/Command/_lua b/Completion/Unix/Command/_lua
new file mode 100644
index 000000000..7254d3819
--- /dev/null
+++ b/Completion/Unix/Command/_lua
@@ -0,0 +1,63 @@
+#compdef lua -P lua[0-9.-]##
+
+# Complete lua library names. We go out of our way here to support sub-modules
+# (of the format foo.bar.baz), even though the way `lua -l` handles those isn't
+# very nice, because it might be useful for informational purposes
+(( $+functions[_lua_libraries] )) ||
+_lua_libraries() {
+ local p pre
+ local -a tmp tmp2
+
+ # Get Lua's library search path
+ tmp=( ${(s<;>)${(@f)"$(
+ _call_program library-path $words[1] -e '"print(package.path)"'
+ )"}} )
+ # Support C modules, which aren't explicitly included in the above
+ tmp+=( ${(@)${(@M)tmp:#*'?.lua'}/%.lua/.so} )
+
+ for p in ${(@u)tmp}; do
+ # Don't recurse infinitely into the current directory; we'll just trust
+ # that all other paths are sensible
+ if [[ $p == './?'* ]]; then
+ tmp=( ${~${${(b)p}/'\?'/'*'}}(#qN) )
+ else
+ tmp=( ${~${${(b)p}/'\?'/'**/*'}}(#qN) )
+ fi
+ tmp2+=( ${(@)tmp##${p%%'?'*}} )
+ done
+
+ tmp=( ${(@)tmp2%%(/init.lua|.lua|.so)} )
+ tmp=( ${(@u)${(@)tmp//\//.}} )
+
+ _wanted -x libraries expl 'Lua library' compadd -a "$@" - tmp
+}
+
+_lua() {
+ local ret=1
+ local -a context expl line state state_descr
+ local -A opt_args
+
+ # Stacking not supported, no arguments are exclusive except `-`
+ _arguments -S -A '-*' : \
+ '*-e+[execute specified command string]:command string' \
+ '-E[ignore environment variables]' \
+ '-i[enter interactive mode]' \
+ '*-l+[specify library or module to require]: :_lua_libraries' \
+ '-v[display version information]' \
+ '(1 -)-[stop argument parsing and execute script on stdin]' \
+ '1:Lua script:_files' \
+ '*:: :->arg' \
+ && ret=0
+
+ [[ $state == arg ]] &&
+ if [[ $line[1] == - ]]; then
+ _description files expl 'script argument'
+ _files "${(@)expl}" && ret=0
+ else
+ _normal && ret=0
+ fi
+
+ return ret
+}
+
+_lua "$@"
prev parent reply other threads:[~2018-07-23 11:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 6:50 dana
2018-07-23 11:40 ` dana [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E01C10CC-1034-4DCE-BC93-9CBAD099703A@dana.is \
--to=dana@dana.is \
--cc=zsh-workers@zsh.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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).