Re: absolute native symlinks vs file explorer on windows 8.1
On Dec 4 22:26, Andras Nagy wrote: > I'm experiencing the following symptom with the latest 64bit cygwin on > windows 8.1: absolute native symlinks created with cygwin differ slightly > from those created with mklink; cygwin's symlinks start with a "\\?\" . > Because of this, file explorer (nee windows explorer) refuses to handle them > properly, specifically, nothing happens when I double click on such a > symlink. See exact repro below. > > Cygwin exhibits the same behavior on windows 7, but windows 7's explorer > handles such symlinks fine. It also works fine on Windows Vista and Windows 8. This is most certainly a bug in Windows 8.1. Cygwin uses the official OS function CreateSymbolicLinkW[1], which handles the \\?\ prefix and thus long pathnames just fine. CMD and the rest of the Windows 8.1 OS handles symlinks with long path prefix correctly (try: cmd /c type v1.txt). Only the ShellExecuteW function seems to be broken now. > Questions: > - Why does the target of the native cygwin symlink start with "\\?\" ? Long path prefix[2]. > - Is there a way to make cygwin not add that prefix to native symlinks? No, because it always worked so far. We were not aware that Micorsoft broke this functionality on Windows 8.1. > - Alternatively, is there a way to make windows 8's file explorer behave > like windows 7's explorer and tolerate such native symlinks? This question you have to ask Microsoft. We could workaround this in the next Cygwin version at least for short paths < 260 chars by omitting the \\?\ prefix in this case. It wouldn't be the first OS bug we have to workaround, but it's kind of annoying even so. I'm going to discuss this bug in the Microsoft forums[3], maybe it will get fixed in upcoming versions of Windows again. I don't think we will ever see a fix for 8.1, though. Thanks, Corinna [1] http://msdn.microsoft.com/en-us/library/windows/desktop/aa363866%28v=vs.85%29.aspx [2] http://msdn.microsoft.com/en-us/library/windows/desktop/aa365247%28v=vs.85%29.aspx#maxpath [3] http://social.msdn.microsoft.com/Forums/en-US/073d02a6-1181-4694-9e50-d6a05bd80663/shellexecutew-w-symlinks-broken-on-windows-81?forum=windowsgeneraldevelopmentissues -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgph3qZ5WZf_s.pgp Description: PGP signature
Re: emacs won't run
On 12/04/13 16:50, David Karr wrote: Are you running it from the desktop from "run"? I discovered the same thing. One workaround that worked for me was to open a rxvt window and then run emacs from that. I tried from xterm or "Cygwin Terminal". However, an even better workaround was simply using the "w32" version and bypassing X entirely. I know, but this is not the exactly the same. bye & Thnanks av. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: emacs won't run
On 12/04/13 11:56, marco atzeri wrote: Il 12/4/2013 10:20 AM, Andrea Venturoli ha scritto: Hello. Since a bit, emacs won't start under X: no error, no message, nothing. It just starts and exits after a while without doing anything. I can run "emacs -nw" fine. How can I diagnose this? Is there any log I can look into? Any utility? bye & Thanks av. use strace. Thanks. Forgive my noobiness, but... > strace emacs > strace.exe error creating process emacs, (error 2) Of course, emacs is a shell script. So I run "strace emacs-x11": is this ok? Running emacs-x11 by itself I get one of two behaviours: a) either it hogs the CPU for some seconds, then quits with no effect at all; b) or it hogs the CPU for a while, then I'll get "Memory exhausted--use M-x save-some-buffers then exit and restart Emacs". I still can't grasp what makes the difference. Running it through strace, however, it never exits (still doing nothing appreciable); it is also quite hard to kill. In the end I got a trace file (which is over 7MB!), but it's nothing I can interpret. What should I do? Anything I should look for? Any way to make some sense out of this? Should I upload it somewhere for someone who might be interested in seeing it? bye & Thanks av. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: emacs won't run
Il 12/5/2013 1:50 PM, Andrea Venturoli ha scritto: On 12/04/13 11:56, marco atzeri wrote: Il 12/4/2013 10:20 AM, Andrea Venturoli ha scritto: Hello. Since a bit, emacs won't start under X: no error, no message, nothing. It just starts and exits after a while without doing anything. I can run "emacs -nw" fine. How can I diagnose this? Is there any log I can look into? Any utility? bye & Thanks av. use strace. Thanks. Forgive my noobiness, but... > strace emacs > strace.exe error creating process emacs, (error 2) Of course, emacs is a shell script. So I run "strace emacs-x11": is this ok? should be. Running emacs-x11 by itself I get one of two behaviours: a) either it hogs the CPU for some seconds, then quits with no effect at all; b) or it hogs the CPU for a while, then I'll get "Memory exhausted--use M-x save-some-buffers then exit and restart Emacs". I still can't grasp what makes the difference. Running it through strace, however, it never exits (still doing nothing appreciable); it is also quite hard to kill. In the end I got a trace file (which is over 7MB!), but it's nothing I can interpret. What should I do? Anything I should look for? any seriuos error ;-) Any way to make some sense out of this? Should I upload it somewhere for someone who might be interested in seeing it? see here Problem reports: http://cygwin.com/problems.html and follow the "cygcheck -s -v -r > cygcheck.out" point additonal you can upload the trace file somewhere, so someone could take a look -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: emacs won't run
Andrea Venturoli netfence.it> writes: > Of course, emacs is a shell script. Of course it should be a symlink, pointing to emacs-X11 on a standard installation. Did you read /usr/share/doc/emacs/README.Cygwin? Is the DISPLAY environment variable set correctly? Does Emacs "run" when you start it as "emacs-X11 -Q"? Regards, Achim. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Install Bash 4.2 for Cygwin
Hello!! Is possible install bash 4.2 on cygwin? Is there some patch or update for it? Thanks -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated, new for 64-bit: lftp 4.4.11-1
> Achim Gratz NexGo.DE> writes: > > This version seems to have serious problems with the mirror command. > > Instead of transferring just the changed files, it seems to always want to > > transfer _everything_. I haven't yet looked into why this might happen, at > > the moment I've reverted to the previous version. > > The last version to work correctly is 4.4.9, I don't see anything obvious in > the ChangeLog that would explain why this happens. OK. Meanwhile version 4.4.13 is out. Have you tried it to see if the problem is fixed there? If not, I could put it out in test for you to try. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
