From: Jason Tishler <jason@tishler.net>
To: cygwin@cygwin.com
Subject: Re: Mutt 1.4-1 opens mbox read-only
Date: Tue, 30 Jul 2002 17:50:00 -0000 [thread overview]
Message-ID: <20020730195051.GA1324@tishler.net> (raw)
In-Reply-To: <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/
next prev parent reply other threads:[~2002-07-30 19:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-22 14:46 Jens Schuessler
2002-07-24 8:34 ` Jason Tishler
2002-07-24 15:07 ` Jens Schuessler
2002-07-24 15:17 ` Dr. Volker Zell
2002-07-25 5:44 ` Gary R. Van Sickle
2002-07-25 9:20 ` Jason Tishler
2002-07-26 20:08 ` Jens Schuessler
2002-07-30 17:50 ` Jason Tishler [this message]
2002-07-31 5:47 ` Gary R. Van Sickle
2002-07-31 11:10 ` Jens Schuessler
-- strict thread matches above, loose matches on Subject: below --
2002-07-16 18:42 Jens Schuessler
2002-07-12 13:38 news
2002-07-16 1:37 ` Gary R. Van Sickle
2002-07-16 7:09 ` Charles Krug
2002-07-11 12:49 Jens Schuessler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020730195051.GA1324@tishler.net \
--to=jason@tishler.net \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).