busy-vase-39202
08/31/2022, 6:09 PMwide-midnight-78598
08/31/2022, 6:12 PMbusy-vase-39202
08/31/2022, 6:28 PMwide-midnight-78598
08/31/2022, 6:30 PMbusy-vase-39202
08/31/2022, 6:31 PMwide-midnight-78598
08/31/2022, 6:32 PMbusy-vase-39202
08/31/2022, 6:33 PMpantsbuild/pants-completions
...?wide-midnight-78598
08/31/2022, 6:36 PM./pants export
vs something else. I proposed, somewhere, something like ./pants --completions
busy-vase-39202
08/31/2022, 6:36 PMwide-midnight-78598
08/31/2022, 6:47 PMbusy-vase-39202
08/31/2022, 6:48 PMwide-midnight-78598
08/31/2022, 6:52 PMexport
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 implementproud-dentist-22844
08/31/2022, 8:53 PMpants
from any directory and have it auto-adjust the args such that it can run pants from the root ./pants
under the covers…busy-vase-39202
08/31/2022, 8:56 PMpantsd
prompt. That's such a straightforward contribution for the right person.wide-midnight-78598
08/31/2022, 9:12 PMIt might be cool to have a symbol in the prompt when pantsd is runningWhy? 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
busy-vase-39202
08/31/2022, 9:46 PM--no-pantsd
is a valid choice. https://www.pantsbuild.org/docs/contributions-debuggingwide-midnight-78598
09/01/2022, 12:12 AMproud-dentist-22844
09/01/2022, 12:24 AMwide-midnight-78598
09/01/2022, 12:31 AMbusy-vase-39202
09/01/2022, 1:32 AMwide-midnight-78598
09/01/2022, 1:35 AM