Mail Archives: djgpp/1996/11/27/23:37:50
[The tail of my article was cut off by the news reader. Here's it again.]
Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote in article
<Pine DOT SUN DOT 3 DOT 91 DOT 961127081248 DOT 5811A-100000 AT is>...
>
> On Tue, 26 Nov 1996, David May wrote:
>
> > I lost the original message asking help about changing directory into
> > the c:\Program Files directory under Windows 95 under bash. The
> > only way I could get it to work is to use
> > cd /Progra~1.
> > Then pwd returns
> > /Progra~1
> > as the current working directory.
> >
> > Any ideas?
>
> Since Unix generally doesn't support such directory names, I'd guess
> `bash' fails to support them too. Ideas? Get the `bash' sources and fix
> this problem. Isn't that what free software is all about--to be able to
> fix any problem without waiting for the vendor to get to it?
>
[I posted a false alarm message yesterday regarding bash "cd" command. My
problem was caused by a recursive key macro in .inputrc, which I have
played with but forgot about when I had the problem.]
I had experimented with bash on Windows 3.1[1] and Windows 95 machines.
Here's some findings:
1. bash cannot be installed as a DOS shell.
2. On DOS 6.2 machines, running bash inside COMMAND.COM eats a
considerable amount of DOS memory. On Windows 95 machines this is not a
problem.
3. "cd //c/program\ files" and "cd //c/progra~1" both get me into the
"Program Files" directory, and set the PWD respectively.
4. Filename completion does not work with "//c/..." style files.
5. Windows 3.1 won't start inside bash.
6. bash hangs after certain commands when started from inside Windows 3.1
.
Now if only someone can tell me how to bind the arrow keys to the bash
history commands, I'd post the nifty bash Icon I draw yesterday!!!
--
Weiqi Gao
weiqigao AT crl DOT com
- Raw text -