From: "Jörg Sommer" <joerg@jo-so.de>
To: Oliver Kiddle <opk@zsh.org>
Cc: zsh-users@zsh.org
Subject: Re: How to get all tagets for rake completion?
Date: Sun, 4 Apr 2021 10:28:35 +0200 [thread overview]
Message-ID: <20210404082835.pwkfkoprksgluuqz@jo-so.de> (raw)
In-Reply-To: <53310-1617184228.244862@cFeP.EmJg.7ARq>
[-- Attachment #1: Type: text/plain, Size: 1267 bytes --]
Oliver Kiddle schrieb am Mi 31. Mär, 11:50 (+0200):
> Jörg Sommer wrote:
> > > As a general principle, it is better to use a style name that has a
> > > generic meaning. I can't find any existing style along the lines of an
> > > extra-matches, more-matches, allow-slow-generation etc so unless I've
> > > missed one you'd need to invent a suitable one. "all-targets" is too
> > > specific to targets.
> >
> > How about ‘verbose’?
>
> The existing `verbose` style is usually used to conditionally add
> descriptions to matches, especially where generating those descriptions
> is slow or where they're of questionable value.
And how about ‘expanded’ or ‘extended’?
> Is rake -A giving you a fallback, e.g. "unknown" description for the
> extra targets or does the description remain blank?
The description remains blank. It looks like this:
```
rake www/dev/files/main.min.css # min.css files depend on there js file
rake www/dev/files/main.min.js # The .js file depends on the sources from .js.map / The .min.js fil...
rake www/dev/files/rss # Build main rss file
rake www/dev/files/sync.html #
rake www/dev/nginx.cfg #
```
Regards Jörg
--
Du hast keine Chance – also nutze sie.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 269 bytes --]
next prev parent reply other threads:[~2021-04-04 8:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 12:57 Jörg Sommer
2020-12-15 17:12 ` Peter Stephenson
2020-12-15 21:40 ` Jörg Sommer
2021-03-31 0:10 ` Oliver Kiddle
2021-03-31 7:45 ` Jörg Sommer
2021-03-31 9:50 ` Oliver Kiddle
2021-04-04 8:28 ` Jörg Sommer [this message]
2021-04-08 21:51 ` Oliver Kiddle
2021-04-12 8:07 ` Jörg Sommer
2021-04-25 16:34 ` Lawrence Velázquez
2021-05-02 16:52 ` Lawrence Velázquez
2021-05-09 17:32 ` Lawrence Velázquez
2021-05-10 12:14 ` Daniel Shahaf
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=20210404082835.pwkfkoprksgluuqz@jo-so.de \
--to=joerg@jo-so.de \
--cc=opk@zsh.org \
--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).