(Duarte - I too was surprised there was no library directory setting in preferences, I always put a 'use lib' in my code so it knows where to look).
I've been working with Padre (the windows pack - v.094) on Windows XP, for a few weeks now, and am liking it a lot.
A few minor niggles:
1. The line numbers occasionally get out of sync, possibly due to blank lines, I've not worked it out completely. I often get to the point where I know I have to look 3 or 4 lines down from the marked line. When it gets too bad I quit and reload Padre.
2. The debugger window doesn't size properly on first use (the buttons are too big and don't fit the window), but manually resizing it fixes it - by shrinking the buttons).
3. Padre crashes if you run the debugger with compilation errors, so I always have to do a non-debug run after any change - although now I've switched on the real-time syntax checking that's less of an issue.
4. I've also had a handful of additional crashes that I can't pin a root cause on.
5.The regex editor could be improved a little. (e.g. you cut an m/.../xms from the code and it would extract the regex and set the flags. And show the results of any bracketed groups or array result.
6. I love the realtime syntax checking box, and marking the bad lines with a red blob. But I hate the floating text beneath the line in error - this is constantly causing me to delete/mistype text - since the syntax text moves around so much you find yourself positioning your cursor (with the mouse) in a different place from where you expected to. I can't find an option to disable this.
7. The breakpoints window doesn't update - it stays blank. Breakpoints set with the main toolbar sometimes conflict with breakpoints set with the debugger 'b'. I think the toolbar breakpoint doesn't work while you are debugging, you have to use b. But it's confusing. And the debugger doesn't seem to automatically break on breakpoints in other modules, you have to step through into the module and then press continue. Which is a pain when you're mainly coding in a module and can't just set a breakpoint, start the debugger, and 'c' to the breakpoint.
I notice there's a Padre v0.96 available that might fix some of these, but I have no idea how to upgrade!