git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Feature request: highlight local worktree in `worktree list`

From
Chris Torek <chris.torek@gmail.com>
Date
Mar 21, 2024, 00:53 UTC
Message-ID
<CAPx1Gvf5g3z8E0e6TmwgDc-TVFmTvSBexBGtOwB8+jh-k6G=7g@mail.gmail.com>
In-Reply-To
<63dda239-1205-4aae-a3b2-10365147751c@gmail.com>
On Wed, Mar 20, 2024 at 3:24 PM Rubén Justo <rjusto@gmail.com> wrote:
> "git branch --list" has a much richer machinery than "git worktree list".
> Perhaps the display machinery of both commands can converge in some way.

I have no concrete suggestions for such, but I will note that there is a `git for-each-ref` plumbing command for refs, but no `git for-each-worktree` plumbing command for worktrees. Given the relationship here (each worktree has a worktree-specific set of refs), perhaps that's a point of leverage, as it were?

Chris
Previous: Rubén Justo
Message 7 of 7 in “Feature request: highlight local worktree in `worktree list`”
  1. Matt HickfordMar 20, 2024
  2. Jeff KingMar 20, 2024
  3. Junio C HamanoMar 20, 2024
  4. Jeff KingMar 20, 2024
  5. Matt HickfordMar 21, 2024
  6. Rubén JustoMar 20, 2024
  7. Chris TorekMar 21, 2024

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.