On Thu, Dec 06, 2001 at 02:14:25PM -0800, David Rothenberger wrote:
>I have no idea why xemacs is calling the function with "/cygdrive" when
>following symlinks like the ones you described, but it does.
>
>Maybe cgf can fix this behavior, too...
I suspect that this is different, unrelated behavio
I think it's related. My little test program shows that when
cygwin_posix_to_win32_path_list() is called with "/cygdrive", it also
returns an empty string. Strangely, "/cydrive/" returns "\".
I have no idea why xemacs is calling the function with "/cygdrive" when
following symlinks like the one
On Thu, Dec 06, 2001 at 11:46:43AM -0800, David Rothenberger wrote:
> I've done a little debugging and here's what I've found out.
>
> It appears to be a problem/change to the behavior of
> cygwin_posix_to_win32_path_list(). When this function is called with a
> path of the form "/cygdrive/z/som
On Thu, Dec 06, 2001 at 11:46:43AM -0800, David Rothenberger wrote:
>I've done a little debugging and here's what I've found out.
>
>It appears to be a problem/change to the behavior of
>cygwin_posix_to_win32_path_list(). When this function is called with a
>path of the form "/cygdrive/z/somethin
I've done a little debugging and here's what I've found out.
It appears to be a problem/change to the behavior of
cygwin_posix_to_win32_path_list(). When this function is called with a
path of the form "/cygdrive/z/something", it returns an empty string
unless the drive "z" actually exists. Thi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06 Dec 2001 19:16:55 +0100 Volker Zell wrote:
>> "Jochen" == Jochen Küpper <[EMAIL PROTECTED]> writes:
Jochen> | C:\cygwin / system binmode
Jochen> | c:/data/home system binmode
Jochen> | c:\tmp /tmp sy
On Thu, Dec 06, 2001 at 10:49:36AM -0500, Christopher Faylor wrote:
> Someone should actually *debug the problem*.
This is what I'm (attempting) to do... just thought I'd alert people to
the problem in case someone already had a fix or workaround before I
invested the time.
I'll let you know wha
On Thu, Dec 06, 2001 at 10:02:21AM +, Peter Keller wrote:
> Hi,
>
> I've had the same problem as Ryan, and I have had to roll back to cygwin
> 1.3.5 as well. I can tell you that the problem has something to do with
> /cygdrive: what I have found is that visiting a file whose path begins
> wit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06 Dec 2001 18:14:42 +0100 Volker Zell wrote:
Not for me:( When I try to open /mnt/o/ I get
,[C-x C-f /mnt/o/ RET]
| Fatal error: assertion failed, file realpath.c, line 81, *name
`
Volker> o XEmacs 21.4 (patch 5) "Civil Service" [Lucid]
> "Charles" == Charles Wilson <[EMAIL PROTECTED]> writes:
Charles> Christopher Faylor wrote:
There has also been some confusion in the cygwin mailing list with another
problem to do with file completion in bash: see
http://sources.redhat.com/ml/cygwin/2001-12/ms
Christopher Faylor wrote:
>>>There has also been some confusion in the cygwin mailing list with another
>>>problem to do with file completion in bash: see
>>>http://sources.redhat.com/ml/cygwin/2001-12/msg00175.html . Fixing the
>>>shell file completion problem has NOT fixed the xemacs problem (a
On Thu, Dec 06, 2001 at 10:49:36AM -0500, Christopher Faylor wrote:
>On Thu, Dec 06, 2001 at 10:02:21AM +, Peter Keller wrote:
>>There has also been some confusion in the cygwin mailing list with another
>>problem to do with file completion in bash: see
>>http://sources.redhat.com/ml/cygwin/20
On Thu, Dec 06, 2001 at 10:02:21AM +, Peter Keller wrote:
>There has also been some confusion in the cygwin mailing list with another
>problem to do with file completion in bash: see
>http://sources.redhat.com/ml/cygwin/2001-12/msg00175.html . Fixing the
>shell file completion problem has NOT
Hi,
I've had the same problem as Ryan, and I have had to roll back to cygwin
1.3.5 as well. I can tell you that the problem has something to do with
/cygdrive: what I have found is that visiting a file whose path begins
with /cygdrive using C-x C-f, or using "File->Open..." on a directory that
ha
I read on this list that someone else had problems with xemacs crashing
with 1.3.6. Here is my experience with 1.3.6-3 and xemacs 21.4.5:
anytime I try to visit a file, xemacs simply exits with code 1. It
doesn't crash (at least according to gdb). It simply exits.
Going back to 1.3.5-x fixes
15 matches
Mail list logo
