{"thread":{"id":"8059","subject":"[RFC] Default options","startedAt":"2007-05-09T22:15:15Z","lastAt":"2007-05-09T23:14:32Z","messageCount":3,"participants":["Dana How","Johannes Schindelin","Matthieu Moy"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"41673","messageId":"56b7f5510705091515l7c7090b9rd5599e8746642ef9@mail.gmail.com","threadId":"8059","inReplyTo":null,"subject":"[RFC] Default options","fromName":"Dana How","fromEmail":"danahow@gmail.com","sentAt":"2007-05-09T22:15:15Z","receivedAt":"2007-05-09T22:15:15Z","isPatch":false,"sender":{"key":"danahow@gmail.com","avatar":null},"body":"Reading the exchange about new options to e.g.\ngit gc and git pack-objects over the last few days,\na pattern seemed to emerge.  A new option would be\nproposed,  but then we didn't always want to type it,\nso a corresponding config variable would be added as well.\n\nI notice git supports \"alias.*\" config variables.\nWould it be useful to also support \"options.*\" variables?\nWhen you type\n    git gc <args>\nthis is interpreted as\n    git gc $(git config options.gc) <args>\nso anything in options.gc could be overridden\nby later appearing on the command line.\nThe names might have dashes:\npack-objects would use options.pack-objects .\n\nIf a command is recognized using alias.*,\noptions.* would not be consulted (to keep things simple).\nIn other words, options.* only work for built-ins.\noptions.* would interpret quoting etc in its\nvalue the same way alias.* does.\n\nThus,  you can add a new --option to a program,\nand get a corresponding config variable automatically,\nand without cluttering up the documentation.\n\nI've not yet looked at the git driver code.\nIs there any interest in this feature?\n\nThanks,\n-- \nDana L. How  danahow@gmail.com  +1 650 804 5991 cell\n"},{"id":"41684","messageId":"Pine.LNX.4.64.0705100106250.4167@racer.site","threadId":"8059","inReplyTo":"56b7f5510705091515l7c7090b9rd5599e8746642ef9@mail.gmail.com","subject":"Re: [RFC] Default options","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2007-05-09T23:07:13Z","receivedAt":"2007-05-09T23:07:13Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Wed, 9 May 2007, Dana How wrote:\n\n> I notice git supports \"alias.*\" config variables.\n> Would it be useful to also support \"options.*\" variables?\n\nI would not do it, for the same reason we do not allow to override \nbuiltins via aliases: it breaks scripts.\n\nCiao,\nDscho\n"},{"id":"41685","messageId":"vpqvef1si7b.fsf@bauges.imag.fr","threadId":"8059","inReplyTo":"Pine.LNX.4.64.0705100106250.4167@racer.site","subject":"Re: [RFC] Default options","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@imag.fr","sentAt":"2007-05-09T23:14:32Z","receivedAt":"2007-05-09T23:14:32Z","isPatch":false,"sender":{"key":"git@matthieu-moy.fr","avatar":"https://avatars.githubusercontent.com/u/14709?v=4"},"body":"Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:\n\n> Hi,\n>\n> On Wed, 9 May 2007, Dana How wrote:\n>\n>> I notice git supports \"alias.*\" config variables.\n>> Would it be useful to also support \"options.*\" variables?\n>\n> I would not do it, for the same reason we do not allow to override \n> builtins via aliases: it breaks scripts.\n\nIn any case, I find it a bit redundant with the alias section.\n\nIf I want to be able to quickly type \"git-cmd --some --option\", I'll\njust alias it to something shorter.\n\n-- \nMatthieu\n"}]}