From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: PATCH: Use "make -p" to get targets
Date: Mon, 10 Apr 2000 23:35:03 +0000 [thread overview]
Message-ID: <1000410233504.ZM31215@candle.brasslantern.com> (raw)
I wrote:
> We'll just have to set up a style, as in _diff.
Strictly speaking, the _is_gnu branch would work for Solaris make as well
(as long as nobody actually created a target named .PHONY that had any
real rules). I suppose you can fake it with the version style:
zstyle ':completion:*:make:version' echo GNU
Somebody please "make" a better suggestion.
Index: Doc/Zsh/compsys.yo
===================================================================
@@ -715,6 +715,11 @@
when completing a value out of a set of values (or a list of such
values)
)
+kindex(version, completion tag)
+item(tt(version))(
+used by tt(_call) to look up the command to run to determine the installed
+version of various other commands (currently tt(diff) and tt(make)).
+)
kindex(warnings, completion tag)
item(tt(warnings))(
used to look up the tt(format) style for warnings
Index: Completion/User/_make
===================================================================
@@ -1,7 +1,18 @@
-#compdef make gmake pmake
+#compdef make gmake pmake dmake
local prev="$words[CURRENT-1]" file expl tmp
+(( $+_is_gnu )) || typeset -gA _is_gnu
+
+if (( ! $+_is_gnu[$1] )); then
+ if [[ $(_call version $1 -v -f /dev/null </dev/null 2>/dev/null) = *GNU* ]]
+ then
+ _is_gnu[$1]=yes
+ else
+ _is_gnu[$1]=
+ fi
+fi
+
if [[ "$prev" = -[CI] ]]; then
_files -/
elif [[ "$prev" = -[foW] ]]; then
@@ -14,17 +25,23 @@
file=Makefile
elif [[ -e makefile ]]; then
file=makefile
+ elif [[ -e GNUmakefile ]]; then
+ file=GNUmakefile
else
file=''
fi
if [[ -n "$file" ]] && _wanted targets; then
- tmp=(
- $(awk '/^[a-zA-Z0-9][^\/\t]+:/ {print $1}
+ if [[ -n "$_is_gnu[$1]" ]]; then
+ tmp=( $(make -nsp --no-print-directory -f "$file" .PHONY | awk '/^[a-zA-Z0-9][^\/\t=]+:/ {print $1}' FS=:) )
+ else
+ tmp=(
+ $(awk '/^[a-zA-Z0-9][^\/\t=]+:/ {print $1}
/^\.include *<bsd\.port\.(subdir\.|pre\.)?mk>/ || /^\.include *".*mk\/bsd\.pkg\.(subdir\.)?mk"/ {
print "fetch fetch-list extract patch configure build install reinstall deinstall package describe checkpatch checksum makesum" }' \
FS=: $file)
- )
+ )
+ fi
_all_labels targets expl 'make target' compadd "$tmp[@]" && return 0
fi
compset -P 1 '*='
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next reply other threads:[~2000-04-10 23:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-10 23:35 Bart Schaefer [this message]
2000-04-11 8:20 Sven Wischnowsky
2000-04-11 15:10 ` Bart Schaefer
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=1000410233504.ZM31215@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.auc.dk \
/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).