From: Rob Browning <rlb@cs.utexas.edu>
Subject: "B m" problem still exists in pgnus 0.98 :>
Date: 06 Nov 1999 14:02:49 -0600 [thread overview]
Message-ID: <87ln8bxuae.fsf@raven.localnet> (raw)
I've had this problem for a *long* time, but we never have been able
to track it down. Instructions on how to trigger it on my system are
reproduced below. Let me know what other information you'd like me to
provide. Before I do the followup, "B m" works fine.
run emacs
M-x gnus-no-server
Compose a message to self and send.
gnus-group-get-new-news
Enter inbox
Read new message (gets marked as expired automagically)
gnus-summary-followup-with-original
Compose and send followup
Use "B m" to try and move that article to any other group.
Result is:
Signaling: (file-error "Opening directory" "no such file or directory" "/home/rlb/.gnus/inbox/")
directory-files("/home/rlb/.gnus/inbox/" nil "^\\([0-9]+\\)\\(\\.Z\\(~\\|\\.~[0-9]+~\\)?\\'\\|\\.bz2\\'\\|\\.tgz\\'\\|\\.gz\\(~\\|\\.~[0-9]+~\\)?\\'\\)?" t)
apply(directory-files ("/home/rlb/.gnus/inbox/" nil "^\\([0-9]+\\)\\(\\.Z\\(~\\|\\.~[0-9]+~\\)?\\'\\|\\.bz2\\'\\|\\.tgz\\'\\|\\.gz\\(~\\|\\.~[0-9]+~\\)?\\'\\)?" t))
nnheader-directory-files-safe("/home/rlb/.gnus/inbox/" nil "^\\([0-9]+\\)\\(\\.Z\\(~\\|\\.~[0-9]+~\\)?\\'\\|\\.bz2\\'\\|\\.tgz\\'\\|\\.gz\\(~\\|\\.~[0-9]+~\\)?\\'\\)?" t)
nnheader-article-to-file-alist("/home/rlb/.gnus/inbox/")
nnml-update-file-alist()
nnml-request-move-article(35149 "inbox" "rlb+nnml+rlb:inbox" (gnus-request-accept-article "nnml+rlb:gnucash" (quote nil) t t) t)
gnus-request-move-article(35149 "nnml+rlb:inbox" "rlb+nnml+rlb:inbox" (gnus-request-accept-article "nnml+rlb:gnucash" (quote nil) t t) t)
gnus-summary-move-article(nil)
call-interactively(gnus-summary-move-article)
Thanks
--
Rob Browning <rlb@cs.utexas.edu> PGP=E80E0D04F521A094 532B97F5D64E3930
next reply other threads:[~1999-11-06 20:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-06 20:02 Rob Browning [this message]
1999-11-11 3:23 ` Lars Magne Ingebrigtsen
1999-11-12 20:26 ` Rob Browning
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=87ln8bxuae.fsf@raven.localnet \
--to=rlb@cs.utexas.edu \
/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).