Re: [RFC PATCH 0/5] Introduce -t, --table for status/add commands

From: Dragan Simic <dsimic@manjaro.org>
Date: Oct 24, 2023, 01:10 UTC
Message-ID: <62164acf4a787042dbb6e5abe212559b@manjaro.org>
In-Reply-To: <ZTb/HeILRHnZjaz6.jacob@initialcommit.io>

On 2023-10-24 01:17, Jacob Stopak wrote:

Show 13 quoted lines

> That's true, it would be just as easy to report the results of a 
> command
> (and even easier in some cases) than forecasting the result in a 
> dry-run.
> The question is how to decide which one? Do you report the results of
> certain commands by default while hints are enabled? And only as a dry 
> run
> when the --dry-run / -n flag is added? That actually would make sense 
> as
> it wouldn't add "special" behavior to the dry run. The dry run would 
> just
> report the exact same default output as the normal command, but omit 
> the action.

IMHO, it would be the best to simply implement support for "<command>.verbose = table" in the git configuration, similarly to how we already have "commit.verbose = true". That way tables could be enabled per command, according to the user's preferences, regardless of performing dry runs or not.

The new hint would be placed somewhere, which should be decided separately, but having the hint enabled or disabled wouldn't affect anything else. Just like with the other hints.