From: "Jun T." <takimoto-j@kba.biglobe.ne.jp>
To: "zsh-users@zsh.org" <zsh-users@zsh.org>
Subject: Re: Makefile completion with wildcard targets
Date: Tue, 28 Jul 2015 22:11:49 +0900 [thread overview]
Message-ID: <D1518B67-B1C5-45F3-BDF1-0326BDEFA64E@kba.biglobe.ne.jp> (raw)
In-Reply-To: <150727111317.ZM6876@torch.brasslantern.com>
On 2015/07/28, at 3:13, Bart Schaefer <schaefer@brasslantern.com> wrote:
> Should we just make this change in the distribution?
Probably, because if the target has meta-characters like # or ^
then we can use
% make '<TAB>
But while I was testing I found another (independent) problem:
the function _make-expandVars() is not working at all.
I'll continue this subject on the zsh-workers list.
next prev parent reply other threads:[~2015-07-28 13:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 16:47 Andri Möll
2015-07-27 18:13 ` Bart Schaefer
2015-07-28 13:11 ` Jun T. [this message]
2015-09-30 9:23 ` Andri Möll
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=D1518B67-B1C5-45F3-BDF1-0326BDEFA64E@kba.biglobe.ne.jp \
--to=takimoto-j@kba.biglobe.ne.jp \
--cc=zsh-users@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).