On Wed, Jan 13, 2016 at 04:33:57PM -0500, Christopher Browne wrote:
> On Wed, Jan 13, 2016 at 1:43 PM, David Fetter <david at fetter.org> wrote:
> 
> > Folks,
> >
> > Is there a reason other than lack of tuits why $Subject is not already
> > the case?  If not, I'd like to prepare a patch for the next minor
> > release to address it.
> >
> 
> The mild contraindication, to my mind, was that when we set up the -f
> option to allow pulling substantially all configuration (save for the -f
> value!)
> from a file, I thought it would be preferable to pull config from files,
> hence meaning there wasn't much reason to put any tuits into the
> matter.

The altperl tools, and probably others, are not super fun to operate
when only some of the options are settable from the command line.

Then there's the consistency issue, although that's mostly aesthetic.

> With the bit of "contraindication" that it's traditionally tempting to have
> short option names, hence leading to potential fights over what "-s" stands
> for.

I'm happy to add in some form of getopt_long, which I generally prefer
for self-documentation purposes.  Do we need to do something special
the way PostgreSQL does?  I presume simply mandating GNU wouldn't
work.

> If you're keen on patching in long-ish option names for everything,
> I don't see a big reason to struggle against that.

I'd be delighted to improve the clarity here.

Cheers,
David.
-- 
David Fetter <david at fetter.org> http://fetter.org/
Phone: +1 415 235 3778  AIM: dfetter666  Yahoo!: dfetter
Skype: davidfetter      XMPP: david.fetter at gmail.com

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate