Re: [HACKERS] psql -e and -n flags - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [HACKERS] psql -e and -n flags
Date
Msg-id Pine.LNX.4.21.0002062350010.13872-100000@localhost.localdomain
Whole thread Raw
In response to Re: [HACKERS] psql -e and -n flags  (Thomas Lockhart <lockhart@alumni.caltech.edu>)
List pgsql-hackers
On 2000-02-06, Thomas Lockhart mentioned:

> > The suggestion I have is to offer the traditional behaviour with a single
> > -e flag, so there's little change for anyone switching from <7.0, and the
> > "full" echo mode with two -e flags. I'd then change the flags in the
> > regression drivers to -e -e. Comments? Better ideas?
> 
> Hmm. imho having a *count* of switch options being significant is the
> wrong way to go. It gets in the way of things like
> 
> # alias ps psql -e
> # ps -e postgres
> 
> where someone has defined a "convenience" alias for everyone and
> someone else uses it later. Also, it is a style of switch invocation
> not appearing elsewhere afaik.

I don't like it either, but I wasn't sure of a better way.

> 
> I'd suggest a switch style like "-ee" or "-eb" (backend) or "-ev"
> (verbatim) or ??? Comments?

Well that is an option style that doesn't appear anywhere either other
than perhaps find(1). getopt() would read "-ee" exactly as "-e -e", a
behaviour which conforms to POSIX and GNU and ROW (rest of world).

-- 
Peter Eisentraut                  Sernanders väg 10:115
peter_e@gmx.net                   75262 Uppsala
http://yi.org/peter-e/            Sweden




pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] psql -e and -n flags
Next
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] psql -e and -n flags