From: Robert Haas on 4 Aug 2010 21:32 On Wed, Aug 4, 2010 at 8:50 PM, Greg Stark <gsstark(a)mit.edu> wrote: > On Wed, Aug 4, 2010 at 3:35 PM, Tom Lane <tgl(a)sss.pgh.pa.us> wrote: >> Well, the thing about $EDITOR is that it's a very-widely-understood >> convention. �This one won't be, so the argument for making it an >> environment variable seems pretty thin. > > Fwiw the +linenumber convention has been part of $EDITOR since > basically as long as vi has existed. What precisely do you mean by that? We've pretty much established that the convention is nothing like universally accepted by the editors that are out there. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Tom Lane on 4 Aug 2010 22:31 Robert Haas <robertmhaas(a)gmail.com> writes: > On Wed, Aug 4, 2010 at 8:50 PM, Greg Stark <gsstark(a)mit.edu> wrote: >> On Wed, Aug 4, 2010 at 3:35 PM, Tom Lane <tgl(a)sss.pgh.pa.us> wrote: >>> Well, the thing about $EDITOR is that it's a very-widely-understood >>> convention. �This one won't be, so the argument for making it an >>> environment variable seems pretty thin. >> >> Fwiw the +linenumber convention has been part of $EDITOR since >> basically as long as vi has existed. > What precisely do you mean by that? We've pretty much established > that the convention is nothing like universally accepted by the > editors that are out there. More to the point, what I was saying is that there is no convention out there for a second environment variable that tells programs calling $EDITOR how to specify a linenumber argument. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
First
|
Prev
|
Pages: 1 2 3 4 5 6 7 Prev: lock_timeout GUC patch - Review Next: Some git conversion issues |