The change log of jEdit 4.2pre7 says:

> The "Search in Directory" command now always selects the most recently
> searched in directory. To search in the current directory with the
> filter based on the current buffer's file name, click the
> "Synchronize" button.

For me this is an unlucky solution because I have to search in the directory of the current buffer in 99% of all cases.

I would suggest something like a small combobox to switch between these options:

- Search in most recently searched directory
- Search in the directory of the current buffer

When opening the dialog or changing this option the directory depending on the setting is inserted.

I allways uncompress the jedit.jar files - replace the icons by the colored ones and compress it again --- It would de good to include the colored icons in future installations

Thanks to the great job of all jedit developers

I would be very intersted in Markers being persisted. The idea is that if I set markers here and there, I would like them to remain set for all time...

Put the cursor on a Variable and the Variable is highlighted everywehere in the active View

I think if Filesystem browser has "File/Directory import and export from/to local filesystem" feature, jEdit could be a very nice FTP(or some other VFS's) cilent.

Today I spend some time finding a new PHP editor, because the ones I currently use (Quanta and TSwebeditor) are far from perfect. From all the ones I tried Jedit came out best. It has almost all I need and it's great that I can use it on both operating systems I use (Linux and W2K).

There's only one thing I miss in Jedit, and on the net I found more people complaining about Jedit lacking this option. The thing I miss is a PHP function tree. If I have a long PHP file with lots of functions, it's very usefull to have a list of all those funtions somewhere on your screen, so you can switch to a particular function by clicking on it. This saves a lot of scrolling. Here is a screenshot of a TSwebeditor with a function list: http://194.112.147.2/tswebeditor/img/s/10.png

Hi,

The XPath plug-in is a good idea, however it is relatively useless and I hardly ever use it purely because you cannot perform XPath queries relative to a specific node (they are always executed relative to the root node) and therefore you can never test out and optimise your XPath queries. For example:

If I had the some XML representing a page and the current node I was matching (using XSLT for example) was the "body" node, but I wanted to find out the title of the page from this node the best way to do this would be to use the query "ancestor::page/@title". However this is not possible to test in the current XPath plugin.