Quoting Adam Doppelt <amd@...>:
> Hi guys. I downloaded the 2004 MSYS release recently, primarily to
> get bash. I fired up bash but immediately ran into problems trying to
> tab complete on C:/XYZ style path names. I'm used to using filenames
> in this fashion after many years with win32 tcsh.
$ cat .inputrc
set editing-mode vi
> I dug into the bash source and I was able to find and fix several
> problems related to path completion under MSYS. There are still a few
> issues with the 2004 release:
> 1. I use mapped drives a lot to talk to my linux box. For example G:
> => //something/here. If I try to use /g/somefile.txt, MSYS
> incorrectly turns it into <PATHTOMSYS>/g/somefile.txt.
If you add the drive mapping after MSYS has started this is a known
issue. If you touch /etc/fstab or restart MSYS it will workaround the
> 2. The tools shipped with MSYS (cp/mv/ls) refuse to use mapped
> network drives, no matter what format I use (g:/somefile.txt or
Same answer as for issue one.
> I tried to fix (1) by tracing into the spawn.cc source inside the
> msys DLL. I used the latest CVS MSYS rt sources. Unfortunately, bash
> (the 2004 bash) pinned the CPU and hung when I tried to run it
> against my new DLL. I'm not sure how to fix (2).
Hello and welcome. It is nice to hear someone actually looking at the source.
> That leads to my questions...
> * Should I bother reporting bugs? Are there any plans for a new release?
Yes, reporting bugs is a good thing. I have been working this week in
testing the changes that exist in CVS between 1.0.10 and HEAD. I've
discovered a race condition that is giving me headaches with
"Permission denied" errors. I'm still trying to trace it down but I've
managed to minimize it by reverting some of the changes. I thought I
had the issue managed but another test last night proved that I still
have an occasional issue. I have not found the race yet but it seems
to be with the stat and lstat functions from the syscalls.cc source.
> * Does anyone have any suggestions for the hang I encountered in
> (1)? I could probably hack around the problem by making more
> changes to bash, but that seems undesirable.
Hopefully I've pointed you in the correct direction. If my suggestions
don't work for you then I need to understand your problem more.
> * Any suggestions for fixing (2)?
If you wish to look at path.cc and the mount methods to provide an
event thread that will refresh the mount_table with the new data when a
new drive map is added I'll consider it for the 1.0.12 version. The
only changes I want to HEAD at the moment are those that resolve this
race issue. I want to get 1.0.11 released and out of the way.
> I don't like /cygwin and I was very excited to find MSYS. Thanks for
> all your hard work!
You're welcome. I began using Cygwin back in the days when it was
still considered beta. Then it was small, manageable and provided me
with just enough options to learn C/C++. After it became an official
release and it began to grow, providing the user with too many options
to quickly know what was best; I decided that what I wanted was
something much smaller and with fewer choices. So I set out to create
MSYS and gave it a goal of providing just enough to execute a typical
configure script as that is all I needed it to do.
Thank you for being interested enough to search the source. I will be
looking forward to working with you. You have just made my day