Use of # character in temporary buffer names
Submitted by Sunday, 4 March, 2007 - 22:40
on
Not sure if this is a bug, but it's a problem for me.
I'm trying to use Infoviewer to view the output of an XLST transformation.
But the output of this transformation is placed into a temporary buffer, with a name that looks like '#Untitled-1#'.
Infoviewer appears to be treating the buffer name which it is fed as a URL. The presence of the '#', which is an unsafe character in a URL, therefore causes it to display a directory listing for the path up to the '#', which is perfectly reasonable behaviour for a browser under normal circumstances.
I can see two possible resolutions to this.
Firstly, Infoviewer treats a buffer name ( as opposed to a file name ) as something other than a URL. Might be architecturally tricky.
Secondly, JEdit ( if it is JEdit, as opposed to the XSLT transformer ) doesn't autogenerate temporary buffer/file names which would be invalid in URL's. This seems eminently reasonable.
So, what does the committee think - is this a bug ( and if so in what ? ), or a feature request ?
And on a related note, does anyone know a better way of achieving what I want to achieve ( automatic HTML preview of XSLT transformer output ) ?
Thanks,
Mark
I'm trying to use Infoviewer to view the output of an XLST transformation.
But the output of this transformation is placed into a temporary buffer, with a name that looks like '#Untitled-1#'.
Infoviewer appears to be treating the buffer name which it is fed as a URL. The presence of the '#', which is an unsafe character in a URL, therefore causes it to display a directory listing for the path up to the '#', which is perfectly reasonable behaviour for a browser under normal circumstances.
I can see two possible resolutions to this.
Firstly, Infoviewer treats a buffer name ( as opposed to a file name ) as something other than a URL. Might be architecturally tricky.
Secondly, JEdit ( if it is JEdit, as opposed to the XSLT transformer ) doesn't autogenerate temporary buffer/file names which would be invalid in URL's. This seems eminently reasonable.
So, what does the committee think - is this a bug ( and if so in what ? ), or a feature request ?
And on a related note, does anyone know a better way of achieving what I want to achieve ( automatic HTML preview of XSLT transformer output ) ?
Thanks,
Mark