Re: psql possible TODO - Mailing list pgsql-hackers

From Svenne Krap
Subject Re: psql possible TODO
Date
Msg-id 4575F84A.3010802@krap.dk
Whole thread Raw
In response to Re: psql possible TODO  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> We've got that: control-R xyz.
>
> The thing I'm having a hard time with here is the notion that command
> number is a convenient way of identifying prior commands.  It seems like
> an idea that should have gone out with punched cards.
>   
Command-numbers are the point-and-click equivalent for mouse-less users :)

Well... sometimes I can remember the pattern of something I wrote some 
(for the sake of the argument a few hundred ) commands ago, but nothing 
verbatim.
Seeing the full history (with large scrollback buffer in the console 
app), I quickly spot the command I need.

I could at that time just as easily see, that number 317 would refer to 
that command, and I wish to load that number in my editor.

I would really hate to have to backstep a few hundred commands, or 
reverse search if I have nothing specific enough to search for (say the 
last 50 commands where all alike - sorta the same tables and columns).

btw. Readline has history too.. 
http://tiswww.case.edu/~chet/readline/history.html

+1 from a lurking user :)

Svenne

pgsql-hackers by date:

Previous
From: "Simon Riggs"
Date:
Subject: Re: Configuring BLCKSZ and XLOGSEGSZ (in 8.3)
Next
From: Andrew - Supernews
Date:
Subject: Re: how to find index columns