* emacsclient x:foo
@ 2008-02-20 12:22 Juanma Barranquero
0 siblings, 0 replies; only message in thread
From: Juanma Barranquero @ 2008-02-20 12:22 UTC (permalink / raw)
To: Emacs Devel
I've just commited a change to emacsclient on Windows so
X:foo
which was until now understood to be a NTFS filestream, it is now interpreted as
X:/current-directory-on-drive-X/foo
That is more consistent with most programs on Windows, and much more
user friendly (NTFS streams are not often used directly by the user,
while drive-relative filenames are common).
For simplicity, I've processed all relative paths (not just X:foo, but
foo and .\foo and ./foo, for example) through the GetFullPathName API.
AFAICS, that improves consistency; cases where previously Emacs
received X:\foo/bar will now be X:\foo\bar. Absolute paths, like
X:/foo/bar, are still passed unscathed.
All this preamble is to ask: if someone is using a Windows emacsclient
to connect to non-Windows Emacs servers, I'd like to know of any
regressions with respect to filename handling.
Thanks,
Juanma
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2008-02-20 12:22 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-02-20 12:22 emacsclient x:foo Juanma Barranquero
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).