Joshua D. Drake wrote:
> On Tue, 2006-12-05 at 17:45 -0500, Bruce Momjian wrote:
> > Alvaro Herrera wrote:
> > > Tom Lane wrote:
> > > > "Joshua D. Drake" <jd@commandprompt.com> writes:
> > > > > control-R isn't real useful for 17 queries that are exactly the same
> > > > > except for 3 different join clauses. It also isn't useful when you don't
> > > > > know exactly what query you are looking for.
> > > >
> > > > ... but, somehow, you know exactly what command number it has?
> > >
> > > Well, presumably \s would give you the numbers. "history" does on bash anyway.
> > >
> > > I use it on bash all the time: I do "history | grep something" and then
> > > !<number of command I want>.
> > >
> > > I don't think we can do the "| grep" part, but it's useful anyway.
> >
> > OK, now at least I understand how it would be used, and could be
> > explained easily in the documentation --- do \s, then \! 99, or maybe \#
> > 99. I don't like making \! do shells and pull SQL commands from history.
>
> Yeah the # was the next logical thing. Would we have to escape it?
>
> \#12... hmmm
> #12
Well, it is something that controls psql, so the backslash really makes
sense.
-- Bruce Momjian bruce@momjian.us EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +