help / color / mirror / code / Atom feed
From: Oliver Kiddle <opk@zsh.org>
To: "Jörg Sommer" <joerg@jo-so.de>
Cc: zsh-users@zsh.org
Subject: Re: How to get all tagets for rake completion?
Date: Thu, 08 Apr 2021 23:51:43 +0200	[thread overview]
Message-ID: <54621-1617918703.747482@gwX8.ONTM.cKuV> (raw)
In-Reply-To: <20210404082835.pwkfkoprksgluuqz@jo-so.de>

On 4 Apr, Jörg Sommer wrote:
> > 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’?

Either of those are fine. Though you've not commented on the approach of
inverting the sense of the style and using ignore-<something> which I
think I prefer but I don't know rake so well.

Just pick whatever you think is best and update the patch with that and
it should then be good to commit.

> > 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/rss           # Build main rss file
> rake www/dev/files/sync.html     # 

Checking the targets=( ... ) assignment and _describe with that appears
to work fine without any further adjustment.


  reply	other threads:[~2021-04-08 21:53 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
2021-04-08 21:51             ` Oliver Kiddle [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54621-1617918703.747482@gwX8.ONTM.cKuV \
    --to=opk@zsh.org \
    --cc=joerg@jo-so.de \
    --cc=zsh-users@zsh.org \


* 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


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).