jEdit on WinXP, current SVN version
Settings:
BufferSet scope for new editpanes: Global
New BufferSets contain: copy of current BufferSet
Open a XML file and deliberately insert an error. When it is shown in ErrorList, click
on the error message. Instead of jumping the cursor to the error line, a new empty
buffer is created with a wrong filename (the directory from which jEdit was called
is prepended to the path of the original XML file)
| Submitted | hertzhaft - 2008-07-22 - 13:00:48z | Assigned | kerik-sf |
|---|---|---|---|
| Priority | 5 | Category | None |
| Status | Open | Group | None |
| Resolution | None | Visibility | No |
| 2008-07-22 - 13:05:24z kpouer |
Logged In: YES user_id=285591 Originator: NO I'm unable to reproduce that. from where did you load the xml ? |
|---|---|
| 2008-07-22 - 13:11:27z hertzhaft |
Logged In: YES user_id=1037294 Originator: YES OK, I see where the problem could come from. It doesn't happen with normal filesystem locations. The file is loaded from a remote directory in the network, the name starts with a double backslash, like so \\computer-name\c$\some\path\to\file\foobar.xml Afterwards, the filename looks like this U:\cmd\computer-name\c$\some\path\to\file\foobar.xml |
| 2008-07-22 - 15:01:02z ezust |
Logged In: YES user_id=935841 Originator: NO moving to plugin bugs. |
| 2010-05-14 - 11:52:34z kerik-sf |
will test this. Maybe it's been fixed... |
| 2010-08-19 - 05:51:36z |
This happens to me all the time as I work on a lot of XML files that are accessed
on the network via a UNC path and are not mapped to any drive letter. To reproduce on a local machine you can do so using the following steps: 1. From the open file dialog under path type in \\<computer-name>\c$\some\path\to\files, or if you don't know the computer name \\127.0.0.1\c$\some\path\to\files 2. Choose the XML file with the error 3. Click on any listed error You will be taken to a new empty buffer named: %USERPROFILE%\c$\some\path\to\files\<errorfile>.xml |