Matthew wrote:
Yes, but that thread ended a while ago without a clear solution. My first
installation of cygwin worked just fine. Then I installed cygwinX and now I
have these problems. I've tried unistalling X and reinstalling plain cygwin,
but X keeps coming back instead. I don't feel like
Yes, but that thread ended a while ago without a clear solution. My first
installation of cygwin worked just fine. Then I installed cygwinX and now I
have these problems. I've tried unistalling X and reinstalling plain cygwin,
but X keeps coming back instead. I don't feel like cleaning my regis
Lee Maschmeyer wrote:
I've never had ls say it can't read ., but I do remember having path
completion problems. I think that's why I use symbolic links instead of
mount for drives; something like:
cd /
ln -s /cygdrive/c
etc. Then I just cd /c and seldom have to use /cygdrive at all. I'm sure
I've never had ls say it can't read ., but I do remember having path
completion problems. I think that's why I use symbolic links instead of
mount for drives; something like:
cd /
ln -s /cygdrive/c
etc. Then I just cd /c and seldom have to use /cygdrive at all. I'm sure
somebody will explain
On 28 September 2006 15:33, Matthew wrote:
> This issue exists for both the c and d drives. When I cd to the c or d
> drive, I can't tab complete, but once I'm in a subdirectory (say d/Temp)
> tab complete works as well as ls and all that jazz. How can I get cygwin
> to be able to access the con
5 matches
Mail list logo
