From: Corinna Vinschen <vinschen@redhat.com>
To: cygwin@cygwin.com
Cc: vim-dev@vim.org
Subject: Re: small inter-operability patch for vim 6.1.2 for Cygwin
Date: Mon, 22 Apr 2002 12:18:00 -0000 [thread overview]
Message-ID: <20020422211121.B7762@cygbert.vinschen.de> (raw)
In-Reply-To: <200204221835.g3MIZoU02673@moolenaar.net>
On Mon, Apr 22, 2002 at 08:35:50PM +0200, Bram Moolenaar wrote:
> I'm quite sure this is not a good solution. It's just waiting to fail
> in another place. The Unix code just isn't prepared for backslashes in
> a file name to be path separators, they are seen as escaping the special
> meaning of characters.
>
> Why not add something at the start of main() to change backslashes to
> forward slashes? Or better: Isn't there a cygwin trick for this
> already?
Sure:
#include <sys/cygwin.h>
cygwin_conv_to_posix_path(const char *win_path, char *posix_path);
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:cygwin@cygwin.com
Red Hat, Inc.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2002-04-22 19:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-22 11:30 Chris Metcalf
2002-04-22 12:08 ` Bram Moolenaar
2002-04-22 12:14 ` Chris Metcalf
2002-04-22 12:26 ` Corinna Vinschen
2002-04-22 12:18 ` Corinna Vinschen [this message]
2002-04-22 12:31 ` Bram Moolenaar
2002-04-22 12:39 ` small inter-operability patch for vim 6.1.2 for cygwin Christopher Faylor
2002-04-22 14:35 ` Michael A Chase
2002-04-22 14:53 ` Christopher Faylor
2002-04-22 15:27 ` Michael A Chase
2002-04-22 15:30 ` Christopher Faylor
2002-04-22 12:41 ` small inter-operability patch for vim 6.1.2 for Cygwin Corinna Vinschen
2002-04-22 12:44 ` Chris Metcalf
2002-04-22 13:48 ` Bram Moolenaar
2002-04-22 12:41 small inter-operability patch for vim 6.1.2 for cygwin Richard Campbell
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020422211121.B7762@cygbert.vinschen.de \
--to=vinschen@redhat.com \
--cc=cygwin@cygwin.com \
--cc=vim-dev@vim.org \
/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.
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).