Rodney Sparapani wrote:
I can't file a bug report since I'm not an MS Windows user.
But, I was
helping a colleague setup XEmacs on MS Windows and some things are
peculiar, but I suspect they could be fixed easily. For example,
opening a link file gets you a binary mess. Luckily, the actual
filename is in that mess and you can usually copy and paste it to open
the actual file. Can't that be automated?
Also, when you copy that to the minibuffer, you have to edit whatever
was their already. I guess that's because the absolute path of the
filename starts with <drive-letter>: instead of /, ~ or \ (MS
Windows-only, I assume). Could this also be automated just on MS
Windows? I mean something like...
minibuffer before: c:\dir\with\link\<cursor>
minibuffer during: c:\dir\with\link\<paste>c:\actual\filename</paste>
minibuffer after : c:\actual\filename<cursor>
So, in other words, the magic symbols would also need to include a regex
something like [a-zA-Z]:
The xemacs-beta feed has been a little flaky for me lately. So, I'm
just making sure this got out. Of course, maybe no one actually cares
about this. FWIW, this is a stable version, either .20 or .21.
XEmacs-Beta mailing list