Re: [HACKERS] psql -e and -n flags

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: PostgreSQL Development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: [HACKERS] psql -e and -n flags
Date: 2000-02-06 15:54:42
Message-ID: 24524.949852482@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> 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?

Seems reasonable.

> Furthermore, does anyone have anything to say in defence of the -n ("no
> readline") option? If not, I'd be tempted to "hide" it now, since it may
> be a popular option letter to have available in the future.

readline automatically turns off if the input is not coming from a
terminal, right? That seems like the only really compelling reason
to have -n (since you wouldn't want script commands filling your
history or being subject to tab-completion). I suppose someone who
really hated tab-completion might want a way to turn off just that
feature, though --- is there a way?

BTW, if you need one more item for your psql todo list ;-) ... when
looking at EXPLAIN outputs it's possible to get NOTICE messages that
fill many screensful. It might be nice if NOTICEs went through the
pager like query results do.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Don Baccus 2000-02-06 16:03:11 Re: [HACKERS] psql -e and -n flags
Previous Message Tom Lane 2000-02-06 15:47:43 Re: [HACKERS] TODO item