[Bug 57965] Grep tool focuses to last active field rather than to pattern field

[Bill Davenport]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
     
http://bugs.kde.org/show_bug.cgi?id=57965     




------- Additional Comments From bdavnpt2002 at yahoo.com  2003-05-01 18:31 -------
Subject: Re:  Grep tool focuses to last active field rather than to pattern field         

Yep - but copy/paste behavior is hard to unlearn. BTW - it might be reasonable to remove the few references to IGNORE_SCM_DIRS (the #define and a few #ifdef) - the patch I had sent in to implement that mechanism had these to make the code a bit more obvious when I opened it in the editor - they probably shouldn't have made it into the source pool. Also, I'm looking at adding a menu item (so I can create a shortcut) that opens the grep dialog with the text currently in the copy buffer as the pattern to search for (so I can copy, then invoke grep and have the text already in the pattern string - much like the context menu). Should I send that in when complete? Thanks,Bill

Jens Dagerbo <jens.dagerbo at swipnet.se> wrote:------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.

http://bugs.kde.org/show_bug.cgi?id=57965 
jens.dagerbo at swipnet.se changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |FIXED



------- Additional Comments From jens.dagerbo at swipnet.se 2003-05-01 16:57 -------
Yeah, this always annoyed me as well.. Thanks for the patch! :) 

(Btw, you have seen the nifty rightclick menu option for grep, right? Much easier than 
to copy and paste yourself..)

---------------------------------
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.<DIV>Yep - but copy/paste behavior is hard to unlearn. BTW - it might be reasonable to remove the few references to IGNORE_SCM_DIRS (the #define and a few #ifdef) - the patch I had sent in to implement that mechanism had these to make the code a bit more obvious when I opened it in the editor - they probably shouldn't have made it into the source pool.</DIV>
<DIV> </DIV>
<DIV>Also, I'm looking at adding a menu item (so I can create a shortcut) that opens the grep dialog with the text currently in the copy buffer as the pattern to search for (so I can copy, then invoke grep and have the text already in the pattern string - much like the context menu). Should I send that in when complete?</DIV>
<DIV> </DIV>
<DIV>Thanks,</DIV>
<DIV>Bill<BR><BR><B><I>Jens Dagerbo <jens.dagerbo at swipnet.se></I></B> wrote:</DIV>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">------- You are receiving this mail because: -------<BR>You reported the bug, or are watching the reporter.<BR><BR>http://bugs.kde.org/show_bug.cgi?id=57965 <BR>jens.dagerbo at swipnet.se changed:<BR><BR>What |Removed |Added<BR>----------------------------------------------------------------------------<BR>Status|UNCONFIRMED |RESOLVED<BR>Resolution| |FIXED<BR><BR><BR><BR>------- Additional Comments From jens.dagerbo at swipnet.se 2003-05-01 16:57 -------<BR>Yeah, this always annoyed me as well.. Thanks for the patch! :) <BR><BR>(Btw, you have seen the nifty rightclick menu option for grep, right? Much easier than <BR>to copy and paste yourself..)</BLOCKQUOTE><p><hr SIZE=1>
Do you Yahoo!?<br>
<a href="http://us.rd.yahoo.com/search/mailsig/*http://search.yahoo.com">The New Yahoo! Search</a> - Faster. Easier. Bingo.