From: | Robert Haas <robertmhaas(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 00:39:36 |
Message-ID: | BANLkTintzY6GXL-QWcAhCBMjiSmS9XS=yQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, May 21, 2011 at 5:47 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> 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?
It's probably the result of drift between the original patch and what
was eventually committed. IIRC, Pavel had it as an environment
variable originally, but Tom and I didn't feel the feature was
important enough to merit that treatment.
> 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
>
> For powerusers, this could have interesting possibilities.
That's an intriguing possibility. But part of the point of the
original feature was to be able to say:
\ef somefunc 10
...and end up on line 10 of somefunc, perhaps in response to an error
message complaining about that line. I don't think your proposal
would address that.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2011-05-22 00:41:09 | Re: eviscerating the parser |
Previous Message | Robert Haas | 2011-05-22 00:36:42 | Re: eviscerating the parser |