I noticed that there are Oh My Zsh plugins for bazel, please, maven, ant, etc. https://github.com/ohmyzsh/ohmyzsh/wiki/Plugins Would you find it helpful to have a Pants plugin for Oh My Zsh? Are there any specific requests for what Oh My Zsh support of Pants would be? Is anyone interested in contributing?

Related: https://github.com/pantsbuild/pants/issues/16315

Does it make sense to open a ticket for this separately, or does it fall under #16315 already?

16315 is unrelated to ohmyzsh, but relates to completions + pants

I wonder if a Oh My Zsh plugin might make a good first issue for someone who feels more confident in their shell scripting skills than in their deep knowledge of Pants internals. Thoughts?

🤷 The completions are done, it's just a matter of where to put them right now

pantsbuild/pants-completions

...?

I should say, where to generate them. There is a discussion of

./pants export

vs something else. I proposed, somewhere, something like

./pants --completions

Ah. I was literal!

I was imprecise 🙂 They have to be generated on pants.toml change, so a static location is kinda meh. They work nice, I've been using them for a few weeks

Can't wait to see them in action. Is there anything you need from the team in order to move forward?

Just a decision on where they should go.

export

doesn't work at the moment since that's for venvs and such. Otherwise, maybe some opinions on: https://pantsbuild.slack.com/archives/C0D7TNJHL/p1661866801636789 I don't really care where they go - but an idea about whether they should be part of a goal (as a flag or option), or if they can stay separate like the

--completions

idea. I can then go forth and implement

I use oh-my-zsh. zsh completions feel a bit more powerful than bash completions - I wonder if the completions could be retrieved on the fly from a running pantsd to provide contextual completions.

Ooh. Open a ticket for the

pantsd

prompt. That's such a straightforward contribution for the right person.

It might be cool to have a symbol in the prompt when pantsd is running

Why? Shouldn't it always be running if you're using Pants? Also, this does beg the question - does the daemon ever time out? I just opened activity monitor and saw 5 daemons that have been running for a few days

There are some situations where

--no-pantsd

is a valid choice. https://www.pantsbuild.org/docs/contributions-debugging

For sure, I just mean in the context of it modifying the prompt

I was thinking about how I have git and other details on my prompt like, and was wondering how something like that could be useful for pants. I'm not sure if the utility of something that says pantsd is running other than curiosity and maybe debugging... Why were there so many pantsd instances for you? Multiple projects? Or duplicates in the same project?

I like git, because it tells me which branch I'm on - but I find everything else kinda noisy in the ohmyzsh themes. Re: multiple pants instances - good question. I have a lot of projects I've migrated over, but only 2 that I've done anything with in the last week or two. I also noticed that one of them was using my system xcode compiler, and I have NO idea how that happened, since I use a .pants.rc everywhere to ignore that dumpster fire

What if the prompt just had a 👖 or 👖 icon to indicate that Pants is setup in the repo, perhaps with a small modifier such as "*" to additionally indicate that pantsd is running? Essentially the way Github's logo being present in the prompt is a reminder that the repo is setup to use GH.

Oh now that's interesting as a branding/informative hint