# Just Launched: You can now import projects and releases from Google Code onto SourceForge

We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps.

## #1039 ErrorList can't handle UNC pathnames on Windows

closed-works-for-me
Eric Le Lay
None
5
2013-03-04
2008-07-22
Martin Raspe
No

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)

## Discussion

• Logged In: YES
user_id=285591
Originator: NO

I'm unable to reproduce that. from where did you load the xml ?

• Martin Raspe
2008-07-22

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

• Alan Ezust
2008-07-22

• summary: Bufferset / Errorlist bug --> ErrorList can't handle UNC pathnames on Windows

• Alan Ezust
2008-07-22

Logged In: YES
user_id=935841
Originator: NO

moving to plugin bugs.

• Eric Le Lay
2010-05-14

• assigned_to: nobody --> kerik-sf

• Eric Le Lay
2010-05-14

will test this. Maybe it's been fixed...

• Anonymous
2010-08-19

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 \\&lt;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\&lt;errorfile>.xml • Eric Le Lay 2013-03-04 I've tried with a file in \\mycomputer\c$\... and it works fine.

• Eric Le Lay
2013-03-04

• status: open --> closed-works-for-me