From: Lennart Borgman <lennart.borgman@gmail.com>
To: Zeljko Vrba <zvrba.external@zvrba.net>
Cc: 8132@debbugs.gnu.org
Subject: bug#8132: 23.1; comint shell replaces \ in paths with /
Date: Mon, 28 Feb 2011 18:57:11 +0100 [thread overview]
Message-ID: <AANLkTinUMDCEx0tWmx-hrps_kH=VQJ-gsUx4LqWRt6t5@mail.gmail.com> (raw)
In-Reply-To: <4D6BDFAA.30508@zvrba.net>
On Mon, Feb 28, 2011 at 6:47 PM, Zeljko Vrba <zvrba.external@zvrba.net> wrote:
> On 2011-02-28 4:47 PM, Lennart Borgman wrote:
>>
>> Does not most external commands recognize paths with / in them? Which
>> external commands does not do that?
>
>>
> None of the most often used file-manipulation commands do. (See below for a
> transcript). Yes, I know that NTFS in itself allows both / and \ as path
> separators, but, AFAIK, all native (i.e., not ported from unix) command-line
> tools use / as switch.
>
> C:\Users\zvrba>rmdir ../zvrba
> Invalid switch - "zvrba".
>
> C:\Users\zvrba>mkdir ../q
> The syntax of the command is incorrect.
>
> C:\Users\zvrba>del ../zvrba
> Invalid switch - "zvrba".
>
> C:\Users\zvrba>dir ../zvrba
> Invalid switch - "zvrba".
>
> C:\Users\zvrba>copy ../zvrba/.emacs.d/init.el .
> The syntax of the command is incorrect.
>
> C:\Users\zvrba>
Are not these all built in to cmd.exe?
next prev parent reply other threads:[~2011-02-28 17:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-27 13:27 bug#8132: 23.1; comint shell replaces \ in paths with / Zeljko Vrba
2011-02-28 3:32 ` Stefan Monnier
2011-02-28 14:59 ` Zeljko Vrba
2011-02-28 15:47 ` Lennart Borgman
2011-02-28 17:47 ` Zeljko Vrba
2011-02-28 17:57 ` Lennart Borgman [this message]
2011-02-28 22:05 ` Zeljko Vrba
2011-02-28 22:32 ` Lennart Borgman
2011-02-28 18:34 ` Eli Zaretskii
2011-02-28 22:10 ` Zeljko Vrba
2011-02-28 23:04 ` Stefan Monnier
2011-03-01 3:54 ` Eli Zaretskii
2011-03-01 4:48 ` Stefan Monnier
2011-03-01 7:06 ` zvrba
2011-03-01 9:02 ` Michael Albinus
2011-03-01 18:27 ` Eli Zaretskii
2011-03-02 8:42 ` Michael Albinus
2011-03-02 18:41 ` Eli Zaretskii
2011-03-03 9:31 ` Michael Albinus
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='AANLkTinUMDCEx0tWmx-hrps_kH=VQJ-gsUx4LqWRt6t5@mail.gmail.com' \
--to=lennart.borgman@gmail.com \
--cc=8132@debbugs.gnu.org \
--cc=zvrba.external@zvrba.net \
/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).