On Sun, Dec 1, 2019 at 7:08 PM Daniel Shahaf <d.s_at_daniel.shahaf.name> wrote:
> Julian Foad wrote on Sun, Dec 01, 2019 at 12:01:09 +0000:
> > Daniel Shahaf wrote:
> > > I'd like to get the "is this WC mixed revision?" and "is this WC
> switched?" bits without stat()-ing every single file in the worktree.
> >
> > What info do you actually want, functionally? Some info about the WC
> base "shape" like "svn info --x-viewspec" gives?
>
> I use a shell plugin that shows svn/git information above the shell
> prompt. The plugin shows the revision number of the working copy
> checked out in cwd — IIRC, what is shows specifically is the BASE
> revision of ./ — and I'd like to have an indication that the wc is
> mixed-revision.
>
> At the same time, because the plugin assembles its data whenever a new
> prompt is drawn, I'd like the data collection to be fast.
Instead of --no-stat maybe call it --skip-disk-scan which self-explains
what it's supposed to (not) do and implies that it's meant to trade
accuracy for speed?
Some other thoughts...
Instead of parsing and modifying strings when you're trying to answer a
specific question, maybe it could be useful to have a 'svn test' command
that doesn't print anything and uses exit codes to answer questions, like
'svn test --is-mixed-revision-wc'?
Instead of stringing together UNIX commands, (which might not be available
on Windows), maybe it would be useful to have a '--format' argument that
takes printf-like codes and prints custom strings?
Instead of adding this to the client or core binaries, perhaps implement a
standalone program that uses the svn libs to construct prompt strings? It
could be in contrib?
Ideas are a dime a dozen so that's my 3 1/3 cents :-)
Nathan
Received on 2019-12-09 15:04:39 CET