Re: psql possible TODO

It is actually still in my mailbox to be added to TODO when I get up to it.

---------------------------------------------------------------------------

Alvaro Herrera wrote:
> Joshua D. Drake wrote:
> > On Fri, 2006-12-29 at 20:59 -0500, Bruce Momjian wrote:
> > > Alvaro Herrera wrote:
> > > > Tom Lane wrote:
> > > > > Richard Troy <rtroy@ScienceTools.com> writes:
> > > > > > ... it occurs to me that perhaps Josh can implement
> > > > > > a command line switch to turn on command line numbering.
> > > > > 
> > > > > That would solve the problem I have with changing \s.  I think a psql
> > > > > \set variable (comparable to ON_ERROR_STOP and friends) might be the way
> > > > > to go instead of inventing another \-command, but it's not real
> > > > > important.
> > > > 
> > > > So, is anybody working on this?  I think it should be put in the TODO
> > > > list:
> > > > 
> > > >  - Allow psql to display item numbers along each history item, depending
> > > >    on a \set variable
> > > 
> > > I thought Joshua Drake was going to submit a patch, but if doesn't
> > > appear shortly, I will add it to the TODO list with the agreed API.
> > 
> > I will claim this for now. I will let it go if I can't get at least
> > something productive done on it by end of January.
> 
> Now that the embargo period seems to be over, I think it would be a good
> time to add it to the TODO list.  Also, I'd modify the idea slightly to
> allow a more general facility, using %-escapes (or similar) for line
> numbers, dates and so on.  Bash allows something like this (albeit
> limited to only times) using the HISTTIMEFORMAT environment variable.
> 
> This is the first case I know of of an embargo to an agreed TODO item.
> Why was it put in place?  I find it distracting, because the item has to
> be put on someone else's TODO list and then that person has to pinch
> others to get it added to the central TODO list.  Not sure I see the
> point.  (I understand about bashing Joshua ---a sport I also practice in
> Command Prompt's internal lists ;-) --- but in this case it seems to be
> counterproductive).
> 
> -- 
> Alvaro Herrera                                http://www.CommandPrompt.com/
> The PostgreSQL Company - Command Prompt, Inc.
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
>        subscribe-nomail command to majordomo@postgresql.org so that your
>        message can get through to the mailing list cleanly

--  Bruce Momjian   bruce@momjian.us EnterpriseDB    http://www.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +