Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Tue, 30 Jul 2002 15:50:52 -0400
From: Jason Tishler <jason@tishler.net>
Subject: Re: Mutt 1.4-1 opens mbox read-only
In-reply-to: <20020727005422.GA20212@trash.net>
To: cygwin@cygwin.com
Mail-followup-to: cygwin@cygwin.com
Message-id: <20020730195051.GA1324@tishler.net>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline
User-Agent: Mutt/1.4i
References: <20020722202048.GA21538@trash.net>
 <20020724123728.GA1556@tishler.net> <20020727005422.GA20212@trash.net>

Jens,

On Sat, Jul 27, 2002 at 02:54:22AM +0200, Jens Schuessler wrote:
> * Jason Tishler <jason@tishler.net> [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.

Jason

--
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/