From: Francis GALIEGUE <francis@mandrakesoft.com>
To: <zsh-users@sunsite.auc.dk>
Subject: Re: RPM completion in dev19 and a suggested change to make completion
Date: 07 Apr 2000 14:45:09 +0200 [thread overview]
Message-ID: <m3ln2qozai.fsf@toy.mandrakesoft.com> (raw)
In-Reply-To: "Andrej Borsenkow"'s message of "Fri, 7 Apr 2000 15:51:15 +0400"
"Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru> writes:
>
>
> At least, check if it is GNU make or not.
How?
> In my case:
>
> bor@itsrm2% make -p dkfksjkfl |& grep modules
> uninstall.modules:
> uninstall: uninstall.bin uninstall.modules uninstall.man
> uninstall.fns
> .SUFFIXES:install.modules:
> install: install.bin install.modules install.man install.fns
> bor@itsrm2% gmake -p dkfksjkfl |& grep modules
> uninstall.modules:
> install.modules:
> uninstall: uninstall.bin uninstall.modules uninstall.man uninstall.fns
> install: install.bin install.modules install.man install.fns
>
> As you see, GNU make lists install.modules as target but native make
> does not.
>
A little perl will take care of that :) I really resent not having
bzImage as a completion target, and after all, maybe there's a way
make can list all targets without this hack... But the current
limitations of the original script are a nono for me. I always use GNU
make.
> And what happens, if it does have "aaaaa" target? :-)
>
Worst case scenario, but can it ever be ? :)
--
fg
# rm *;o
o: command not found
next prev parent reply other threads:[~2000-04-07 12:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-07 11:19 Francis GALIEGUE
2000-04-07 11:51 ` Andrej Borsenkow
2000-04-07 12:45 ` Francis GALIEGUE [this message]
2000-04-07 12:50 ` Andrej Borsenkow
2000-04-07 13:26 ` Francis GALIEGUE
2000-04-07 16:55 ` Bart Schaefer
2000-04-10 15:02 ` Bart Schaefer
2000-04-07 16:55 ` RPM completion in dev19 and a " Bart Schaefer
2000-04-07 19:10 ` Chmouel Boudjnah
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=m3ln2qozai.fsf@toy.mandrakesoft.com \
--to=francis@mandrakesoft.com \
--cc=zsh-users@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).