From: Ken Brown <kbrown@cornell.edu>
To: Michael Mauger <michael@mauger.com>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: [Emacs-diffs] master 7466a4d: Cygwin emacsclient handles w32 file names
Date: Sat, 04 Jul 2015 11:20:27 -0400 [thread overview]
Message-ID: <5597F9BB.3000809@cornell.edu> (raw)
In-Reply-To: <5595958F.1090400@cornell.edu>
On 7/2/2015 3:48 PM, Ken Brown wrote:
> So I would be much more comfortable with this change if you added a check for a
> file name starting with a drive letter. And it might also be good to add a
> comment explaining the intended use, in which Windows passes a full file path to
> emacsclient.
Something like the following is what I had in mind:
diff --git a/lisp/server.el b/lisp/server.el
index ce19b3c..46687a3 100644
--- a/lisp/server.el
+++ b/lisp/server.el
@@ -1167,8 +1167,11 @@ The following commands are accepted by the client:
(let ((file (pop args-left)))
(if coding-system
(setq file (decode-coding-string file coding-system)))
+ ;; Allow Cygwin's emacsclient to be used as a file
+ ;; handler on MS-Windows, in which case FILENAME
+ ;; might start with a drive letter.
(when (and (eq system-type 'cygwin)
- (fboundp 'cygwin-convert-file-name-from-windows))
+ (string-match "^[A-Za-z]:" file))
(setq file (cygwin-convert-file-name-from-windows file)))
(setq file (expand-file-name file dir))
(push (cons file filepos) files)
Ken
next prev parent reply other threads:[~2015-07-04 15:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150630005924.5663.80677@vcs.savannah.gnu.org>
[not found] ` <E1Z9jtU-0001Tx-85@vcs.savannah.gnu.org>
2015-06-30 2:40 ` [Emacs-diffs] master 7466a4d: Cygwin emacsclient handles w32 file names Ken Brown
2015-06-30 13:56 ` Stefan Monnier
2015-07-01 14:14 ` Ken Brown
2015-07-01 15:47 ` Eli Zaretskii
2015-07-02 2:28 ` Michael Mauger
2015-07-02 19:48 ` Ken Brown
2015-07-04 15:20 ` Ken Brown [this message]
2015-07-04 18:29 ` Stefan Monnier
2015-07-04 19:05 ` Ken Brown
2015-07-07 14:36 ` Ken Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5597F9BB.3000809@cornell.edu \
--to=kbrown@cornell.edu \
--cc=emacs-devel@gnu.org \
--cc=michael@mauger.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).