From: Larry Hall <lhall@rfk.com>
To: Morten Haavaldsen <etomoh@eto.ericsson.se>, gnu-win32@cygnus.com
Subject: Re: Slashes on WIn95 using bash
Date: Mon, 15 Sep 1997 06:25:00 -0000 [thread overview]
Message-ID: <2.2.32.19970915132050.0095179c@ma.ultranet.com> (raw)
At 11:01 AM 9/15/97 +0200, Morten Haavaldsen wrote:
>Hi!
>
>OS: Win95
>
>HOME is set to c:\Morten
>
>Performing ls ~
>gives
>
>c:Morten
>
>Also running the make utility produces same errors with pathnames to
>executables...the slashes are taken away...
>
>Does there exist any variable which can be set ???
>
>Regards,
>Morten
>
I've found ~ is set to the value of HOME prior to any path translation
during the bash startup. Therefore, the backslash disappears because it
is an escape character in *NIX. The only solution I've come up with is
to set HOME to a *NIX style name (/Morten in your case) in Windows. This
will set ~ to /Morten and work as expected. The downside is that HOME is
not in a suitable format for Windows. This is acceptable to me as there
are other variables I can use if I need something similar for Windows
(actually I haven't found such a need yet though.) The one disclaimer
I'll make is that I am working on NT 4.0 + SP3. I don't know if this
would all live another life in 95....
Larry
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
next reply other threads:[~1997-09-15 6:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-15 6:25 Larry Hall [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-09-15 10:57 Sergey Okhapkin
1997-09-15 2:50 Colman Curtin
1997-09-15 1:59 Morten Haavaldsen
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=2.2.32.19970915132050.0095179c@ma.ultranet.com \
--to=lhall@rfk.com \
--cc=etomoh@eto.ericsson.se \
--cc=gnu-win32@cygnus.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.
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).