From: Tak Ota <Takaaki.Ota@am.sony.com>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: handle cygwin path from ldapsearch
Date: Thu, 23 Sep 2004 16:14:11 -0700 (PDT) [thread overview]
Message-ID: <20040923.161411.09475975.Takaaki.Ota@am.sony.com> (raw)
In-Reply-To: <uvfe41tnz.fsf@jasonrumney.net>
Thu, 23 Sep 2004 23:56:16 +0100: Jason Rumney <jasonr@gnu.org> wrote:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
> > Right, but this problem is not specific to ldap but to cygwin.
> > When cygwin built, Emacs understands those filenames.
> > As for cygin-mount.el, it makes non-cygwin Emacs understand those file names
> > as well (by using a file-name-handler that rewrites them to the non-cygwin
> > format).
>
> cygwin-mount.el works transparently, but it is not distributed with
> Emacs, so perhaps it would be better to use convert-standard-filename
> here (and anywhere else that Emacs parses filenames from process
> output).
Aha! That is the perfect function for this. I didn't know the
existence of such function.
BTW, I'm not familiar with cygwin-mount.el but it sounds useful. Is
there a reason why it is not included in emacs? I rely on cygwin
because of its complete coverage and good maintenance. However,
cygwin emacs is much slower and requires X emulation to have graphical
user interface. I believe there is a good demand of using native
emacs (mingw/MSVC built) together with cygwin tools.
-Tak
next prev parent reply other threads:[~2004-09-23 23:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-22 0:47 handle cygwin path from ldapsearch Tak Ota
2004-09-23 20:44 ` Tak Ota
2004-09-23 20:57 ` Stefan Monnier
2004-09-23 21:46 ` Tak Ota
2004-09-23 21:58 ` Stefan Monnier
2004-09-23 22:03 ` Tak Ota
2004-09-24 11:42 ` Stefan
2004-09-23 22:56 ` Jason Rumney
2004-09-23 23:14 ` Tak Ota [this message]
2004-09-23 22:01 ` Tak Ota
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=20040923.161411.09475975.Takaaki.Ota@am.sony.com \
--to=takaaki.ota@am.sony.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).