Re: Inability to delete *or rename* CWD of any program driving me nuts
On Sep 2 14:33, Daniel Colascione wrote: I keep bumping into Cygwin's new inability rename or delete directories that are the CWD of any program. In particular, Emacs will often start background processes like aspell in whatever directory happens to be the default-directory for the current buffer. That program hangs around even after I kill all buffers visiting files in that directory, so even hours after I last edit a file in a directory, I find myself wondering why on earth 'mv' on it hangs. Also, I have (bad?) habit of leaving old terminal windows around, sometimes sitting in directories I later delete or rename. I get rid of them eventually, but having to hunt down and kill them to perform basic filesystem operations is a nuisance. Of course, these annoyances can be worked around, but it was less cumbersome to just allow cwd to be modified. If you read the announcement and followed the discussions on this list, you know why we had to do it. If it helps to share the pain, I don't like it either. Not the faintest. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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: Inability to delete *or rename* CWD of any program driving me nuts
On 9/3/10 12:45 AM, Corinna Vinschen wrote: If you read the announcement and followed the discussions on this list, you know why we had to do it. If it helps to share the pain, I don't like it either. Not the faintest. Of course I have, and I understand the workaround. What I don't understand is why the pipefs technique (for which you had working code, IIRC) wasn't used in the end. Was it the difficulty of changing cygtools to use the new interface? The additional interface complexity? Personally, I'd argue both are worth it. -- 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: Inability to delete *or rename* CWD of any program driving me nuts
On Fri, Sep 03, 2010 at 09:22:40AM -0700, Daniel Colascione wrote: On 9/3/10 12:45 AM, Corinna Vinschen wrote: If you read the announcement and followed the discussions on this list, you know why we had to do it. If it helps to share the pain, I don't like it either. Not the faintest. Of course I have, and I understand the workaround. What I don't understand is why the pipefs technique (for which you had working code, IIRC) wasn't used in the end. Was it the difficulty of changing cygtools to use the new interface? The additional interface complexity? Personally, I'd argue both are worth it. We're already using the pipefs technique. We just aren't making it the default. Since you are subscribed to cygwin-developers, the time to speak up was when this was discussed there rather than trying to rehash the discussion here. cgf -- 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
Inability to delete *or rename* CWD of any program driving me nuts
I keep bumping into Cygwin's new inability rename or delete directories that are the CWD of any program. In particular, Emacs will often start background processes like aspell in whatever directory happens to be the default-directory for the current buffer. That program hangs around even after I kill all buffers visiting files in that directory, so even hours after I last edit a file in a directory, I find myself wondering why on earth 'mv' on it hangs. Also, I have (bad?) habit of leaving old terminal windows around, sometimes sitting in directories I later delete or rename. I get rid of them eventually, but having to hunt down and kill them to perform basic filesystem operations is a nuisance. Of course, these annoyances can be worked around, but it was less cumbersome to just allow cwd to be modified. -- 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
