Re: about EDITOR_LINENUMBER_SWITCH

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: about EDITOR_LINENUMBER_SWITCH
Date: 2011-05-22 04:30:20
Message-ID: BANLkTikn_yujBTvDgz5P2+C1YMUDp77nAA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2011/5/21 Peter Eisentraut <peter_e(at)gmx(dot)net>:
> I noticed the 9.1 release notes claim that the new
> EDITOR_LINENUMBER_SWITCH thing is an environment variable, whereas it is
> actually a psql variable.
>
> This is perhaps sort of a Freudian slip.  Since the editor itself is
> configured using an environment variable, shouldn't any configuration
> about the editor also be an environment variable, so people can
> configure them together?
>
> Another thought is that this whole thing could be done away with if we
> just allowed people to pass through arbitrary options to the editor,
> like
>
> \edit file.sql +50 -a -b -c

in original patch I had to do some magic operation with line number,
so I had to know, what is a line number. A idea with other options are
interesting. More usable can be store these option inside psql
variable (be consistent with current state). Maybe in EDITOR_OPTIONS ?
With possibility to overwrite this options from metacommand

\edit file.sql 10 -x -y -z

Regards

Pavel Stehule

>
> For powerusers, this could have interesting possibilities.
>
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2011-05-22 05:06:04 Re: proposal: enhanced get diagnostics statement
Previous Message Robert Haas 2011-05-22 01:58:03 Re: SSI predicate locking on heap -- tuple or row?