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
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
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 (although
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/something, it
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
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 ones you
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
7 matches
Mail list logo
