Re: about EDITOR_LINENUMBER_SWITCH - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: about EDITOR_LINENUMBER_SWITCH
Date
Msg-id BANLkTikn_yujBTvDgz5P2+C1YMUDp77nAA@mail.gmail.com
Whole thread Raw
In response to about EDITOR_LINENUMBER_SWITCH  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: about EDITOR_LINENUMBER_SWITCH  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
2011/5/21 Peter Eisentraut <peter_e@gmx.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@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: SSI predicate locking on heap -- tuple or row?
Next
From: Pavel Stehule
Date:
Subject: Re: proposal: enhanced get diagnostics statement