From: Laura Conrad <lconrad@laymusic.org>
Subject: Re: error entering cvs gnus
Date: Sun, 19 Aug 2001 07:22:27 -0400 [thread overview]
Message-ID: <m28zgg47m4.fsf@tuba.localdomain> (raw)
In-Reply-To: <iluelq8whmd.fsf@barbar.josefsson.org> (Simon Josefsson's message of "Sun, 19 Aug 2001 10:58:50 +0200")
>>>>> "Simon" == Simon Josefsson <jas@extundo.com> writes:
Simon> Laura Conrad <lconrad@laymusic.org> writes:
>> >> When I try to enter the cvs gnus that I upped this
>> afternoon, I >> get:
>> >>
>> >> Signaling: (file-error "Creating directory" "file exists" >>
>> "/home/lconrad/Mail/world/old")
Simon> So the error message was correct?
The error message may have been correct, but gnus should have
recovered from it and let me in anyway. My complaint was that I
couldn't run gnus at all.
Simon> Hm, what would Gnus do other than to complain?
Let me read my other groups.
Simon> As I see it, the directory where a nnml group lives must
Simon> exist in order to write things into it. If it doesn't
Simon> exist, Gnus tries to create it. I suspect the reason you
Simon> haven't received the error message before is that you
Simon> didn't write to the group (i.e. deleted or inserted
Simon> articles). Would that be right?
This isn't a group that mail gets sorted into; it's the archive group
that mail from another group gets expired into. So I don't see why
gnus should be trying to write to it on entry.
Simon> I don't think there's a bug here.
I disagree; no matter what damn fool thing the user has done she
should still be able to get into gnus.
--
Laura (mailto:lconrad@laymusic.org , http://www.laymusic.org/ )
(617) 661-8097 fax: (801) 365-6574
233 Broadway, Cambridge, MA 02139
next prev parent reply other threads:[~2001-08-19 11:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-18 23:49 Laura Conrad
2001-08-19 0:11 ` Simon Josefsson
2001-08-19 0:48 ` Laura Conrad
2001-08-19 8:58 ` Simon Josefsson
2001-08-19 11:22 ` Laura Conrad [this message]
2001-08-19 12:00 ` Simon Josefsson
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=m28zgg47m4.fsf@tuba.localdomain \
--to=lconrad@laymusic.org \
/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 NNTP newsgroup(s).