From: Andrew Morton <andrewm@uow.edu.au>
To: Bart Schaefer <schaefer@candle.brasslantern.com>
Cc: zsh-users@sunsite.dk
Subject: Re: `make' completion in zsh-3.1.9
Date: Sun, 18 Mar 2001 15:58:52 +1100 [thread overview]
Message-ID: <3AB4408C.18E66E6C@uow.edu.au> (raw)
In-Reply-To: <1010317165153.ZM6844@candle.brasslantern.com>
Bart Schaefer wrote:
>
> On Mar 18, 2:13am, Andrew Morton wrote:
> } Subject: `make' completion in zsh-3.1.9
> }
> } /usr/src/linux> make menu<tab>
> }
> } the shell locks up for about ten seconds, recurring into every
> } directory of the kernel tree doing *something*. Finally,
> } it comes back with `make menuconfig'.
>
> It's running "make -nsp --no-print-directory -f Makefile .PHONY" to cause
> make itself to output the list of possible completions. I don't know why
> this would be taking 10 seconds or more -- it finishes in 1 second or so
> on my machine.
Oh I see. `make -nsp' takes a very long time to complete in the top level of
the kernel tree. It produces 34 megabytes of output.
zsh-3.1.6 does this:
awk /^[a-zA-Z0-9][^\/ \t]+:/ {print $1}
to find potential targets in the makefile, whereas 3.1.9 does this:
if [[ -n "$_is_gnu[$words[1]]" ]]; then
< make -n stuff >
else
<awk '/^[a-zA-Z0-9][^\/\t=]+:/ stuff>
And the 3.1.9 behaviour actually doesn't work properly - it
matches things which can't possibly be built from this directory
such as floppy.c
Ho hum. I'll just edit /usr/share/zsh/3.1.9/functions/User/_make
and put it back the old way.
Thanks.
next prev parent reply other threads:[~2001-03-18 4:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-17 15:13 Andrew Morton
2001-03-17 16:51 ` Bart Schaefer
2001-03-17 18:04 ` Bruce Stephens
2001-03-17 21:02 ` Bart Schaefer
2001-03-17 21:35 ` Bruce Stephens
2001-03-18 4:58 ` Andrew Morton [this message]
2001-03-19 9:34 Sven Wischnowsky
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=3AB4408C.18E66E6C@uow.edu.au \
--to=andrewm@uow.edu.au \
--cc=schaefer@candle.brasslantern.com \
--cc=zsh-users@sunsite.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).