> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Tomi NA
> Sent: 02 June 2006 15:51
> To: pgadmin-support@postgresql.org
> Subject: [pgadmin-support] RFEs: misc find capabilities
> 
> I have a couple suggestions to improve the pgAdminIII tool from my own
> experience.
> 
> 1.) Find-in-page in the help system
> 
> Rationale
> 
> When you search for a keyword in the help documentation, you get a
> list of pages mentioning the keyword. However, pages mentioning the
> keyword can be long themselves and it's hard to scan-read them without
> the possibility to find keyword occurances inside them. I propose
> every mention of a keyword be somehow pointed out (bolded, different
> color, whatever) and/or a find-in-page functionality with a find-next
> function key or hotkey.

The help viewer is part of Windows on Win32, and part of wxWidgets on
other platforms. We have no control over it I'm afraid.

> 2.) A find-again hotkey or keyword in the query editor
> 
> Rationale
> 
> This functionality kind of exist: <Ctrl>-F <Enter> will do the job,
> but I vote for something along the lines of <F3>, the way it's done in
> a lot of other apps.
> 
> 3.) gvim-style, regexp search-replace functionality
> 
> Rationale
> 
> Short of embedding vi in the query editor (the type of *option* I'd be
> thrilled to see), the possibility to do e.g. find all pairs of comma
> separated values - '\(.*\)','\(.*\)' - and replace them with INSERT
> statements - INSERT INTO country_codes (name, code) VALUES ('\1',
> '\2'); - would be great. Of course, I can do all this with a
> copy-paste to my favourite editor, but a
> all-you-need-to-administer-postgresql tool would be better.

Rehashing the search/replace is actually top of my list of projects ATM.
I'm looking at a combined search/replace dialogue, which will have
regexp support (see http://www.yellowbrain.com/stc/regexp.html to get an
idea of what will work with the control we use). F3 will be included of
course.

> I'd appreciate an avalanche of comments. :-)

Sorry, bit of a headache right now - that's about all I can manage :-)

Regards, Dave.

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

               http://www.postgresql.org/docs/faq

Reply via email to