Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Wed, 31 Jul 2002 16:59:28 +0200 From: Jens Schuessler To: cygwin AT cygwin DOT com Subject: Re: Re: Mutt 1.4-1 opens mbox read-only Message-ID: <20020731145928.GA28596@trash.net> Mail-Followup-To: cygwin AT cygwin DOT com References: <20020722202048 DOT GA21538 AT trash DOT net> <20020724123728 DOT GA1556 AT tishler DOT net> <20020727005422 DOT GA20212 AT trash DOT net> <20020730195051 DOT GA1324 AT tishler DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020730195051.GA1324@tishler.net> User-Agent: Mutt/1.3.28i X-Cool: get your free UNIX account @ http://www.trash.net/ * Jason Tishler [30-07-02 21:50]: > Jens, > > On Sat, Jul 27, 2002 at 02:54:22AM +0200, Jens Schuessler wrote: > > * Jason Tishler [24-07-02 14:37]: > > > Please try running mutt_dotlock -t on your mbox. Does it indicate > > > incorrect permissions? > > > > After building the package again with --enable-external-dotlock, I get > > the mutt_dotlock.exe and my mboxes are writeable, everythings fine. > > All mboxes got a "0" on this test. > > I'm glad the mutt is working for you now. However, it would be nice to > better understand why configuring without --enable-external-dotlock > causes this problem. I made the mutt_dotlock-test with the official package installed and echo $? gave me an "0" on all mboxes though they weren't writable by mutt?! So I dont' know what causes this problem with the internal dotlock. Jens -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/