I agree there has been some slight regressions in the feature set of search.
However, as I've worked through Padre doing various polishing my primary focus has been that ALL the niggly details of the features we do have work properly. As we aim for 1.0 we should ensure that we keep the default operating mode of Padre relatively lowest-common-denominator, while ensuring that the added features that makes subsets of users feel at home are simple to turn on as extras. Case insensitive replace is now thus working as intended. I think case preservation should be added a specific additional setting to search (albeit one that you as an Emacs person would be likely to turn on and leave on as the default). Adam On 6 January 2012 03:39, Tom Eliaz <tomel...@gmail.com> wrote: > Hi Adam, all, > > As you may have seen if you track the trac bugs, your recent dialog change > partially fixed an OSX issue where checkmarks in Find/Replace couldn't be > used on OSX - Awesome! > > I have a few questions to throw out there based on my usage of the recent > versions: > > 1. > A Replace dialog issue remains in svn: I cannot use keyboard navigation to > reach the checkmarks in the find or replace dialogs - nor the actual find > next, replace, cancel buttons at the bottom of the dialog. They are only > accessible via the mouse (and Enter does invoke the default action). > > Does anyone else sees the same behavior on other platforms, or is this OSX > specific? > > 2. > Also, I noticed that with find/replace, if case matching is not enabled, the > system will replace upper case letters in a match with lower case letters in > the replace. so if I have text "Test test" and I find/replace test => > text, the result will be "text text". Coming from an emacs background, I > found this a bit counterintuitive. Is this intended behavior, an OSX issue, > or something that needs a bit of code to fix? > > There are still a few OSX issues (and some open areas to investigate) and > I'll try to get a note out about those sometime this weekend. > > Tom > > On Jan 5, 2012, at 3:50 AM, Adam Kennedy wrote: > > Greetings all, and welcome to 2012! > > As I mentioned previously, I think the key for the last few releases > is polishing. > > To this end, I've been working my way back through core features to > make sure they all function smoothly and the way that a typical user > would expect. > > Since the last release, I've been trying to get the five search > dialogs (Find, Find Fast, Find in Files, Replace, Replace in Files) > full functional, and removing features that felt clunky or didn't > work. > > This ended up being a lot more complicated than I expected. I had to > completely rewrite MIME type detection and support, split out all the > Wx-related document type management, and port a number of dialogs over > to wxFormBuilder. > > But I'm happy to report that (except for some final niggles) I've > completed the polishing of the search and replace code now. > > So from my side of things, I'm ready to do a new release once other > people have had a play with it and the final little bugs are worked > out. > > This next release also has the new debugger, and I think we should get > that out ASAP and get people playing with it, so we have time for a > bug fixing round before 1.0. > > Adam > _______________________________________________ > Padre-dev mailing list > Padre-dev@perlide.org > http://mail.perlide.org/mailman/listinfo/padre-dev > > > > _______________________________________________ > Padre-dev mailing list > Padre-dev@perlide.org > http://mail.perlide.org/mailman/listinfo/padre-dev > _______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
