On Fri, May 09, 2014 at 10:02:07AM +0300, jari wrote: > On 2014-05-09 00:23, Martin Quinson wrote: > | Hello Jari, > | > | thanks for the feedback on this bug, but I think that making all > | commands accept the --color flag even if they don't use it would be > | wrong. Actually, you can already setup the colors in quilt. Simply, > | instead of using a bash alias, you should use a ~/.quiltrc file. > | > | Here is mine for example: > | > | QUILT_DIFF_ARGS="--color --show-c-function -p" > | QUILT_SERIES_ARGS="--color" > | QUILT_REFRESH_ARGS="-p ab --diffstat" > | QUILT_NO_DIFF_TIMESTAMPS=1 > > Well. While this is one possibilty, fiddling with various environment > variables and searching manual pages for commands that might accept > color is not the best user friendly UI design. > > The user would simply want to use option > > --color > > The program should just use it or ignore if it does nothing (or is > not yet implented) for the command given.
If I install the example quiltrc in etc, the default behavior will be to activate the colors. Would it fit your needs? I could also make the --color=auto the default setting. I'm really reluctant to add useless parameters to the quilt subcommands, that are organized exactly as git ones. These are more separate but interacting commands than a uniq program. Bye, Mt. -- C'est en voulant connaître toujours davantage qu'on se rend compte qu'on ne sait pas grand-chose. -- Pierre Dac
signature.asc
Description: Digital signature
