Hi, Based on some inputs from dak/eliz and some extra digging into Elisp, I have the following version which can show good improvements in the behaviour from user point of view (in comparision wrt XE
Hello, It should match: "\\" or "//" , which is basically 2 forward/backward slashes In normal regexp: I would have used: ^(\\\\|//) or as dak suggested: (string-match "^\(//\|\\\\\\\\\)") This just
AFAIK, Windows behaves the same no matter if you pass it a forward slash or a backslash. But a UNC _must_ start with two of them, so "^[/\\]" is not good enough. It should be "^[/\\][/\\]" or someth
That's not the same. The first matches either // or \ at the start of a filename, the latter matches either / or \ at the start of a filename. I don't know the context, though: maybe the second actua
Hello, On Fri, 16 Jul 2004 08:22:01 -0500, "Peter Lee" <address@hidden> said: I just realised that XEmacs does something like find-file-literally (and a little more, I guess). If I use find-file-lite
Dhruva> Hello, I find accessing a file usingUNCpathusing GNU Dhruva> Emacs (CVS Head, W2K and MinGW32 build) very slow when Dhruva> compared to XEmacs. Has anyone experienced the same and Dhruva>
Hello, I find accessing a file usingUNCpathusing GNU Emacs (CVS Head, W2K and MinGW32 build) very slow when compared to XEmacs. Has anyone experienced the same and explored the reason? Since I wor