From: Vladimir Volovich <vvv@vvv.vsu.ru>
Subject: bug: coding system for mbox?
Date: 01 Oct 1998 09:15:22 +0400 [thread overview]
Message-ID: <m3k92k2785.fsf@vvv.vsu.ru> (raw)
In-Reply-To: Vladimir Volovich's message of "30 Sep 1998 00:29:31 +0400"
Hello,
Vladimir Volovich <vvv@vvv.vsu.ru> writes:
> something strange happened. i pressed "g" in a group buffer to get new
> mail, but Emacs asked "Revisit the file literally?" (what does it mean
> and why this happened?). I answered yes. Then the history of my nnmbox
> groups was broken.
This error happens each time gnus tries to read mail from mbox. In
particular, each time i start gnus. :-( I.e. i start emacs with the
following ~/.emacs file:
---------------------------
(set-default-font "fontset-standard")
(set-language-environment "Cyrillic-KOI8")
(setq nnmail-delete-incoming t)
(setq rfc2047-default-charset 'koi8-r)
(setq gnus-select-method '(nntp "localhost"))
(setq gnus-secondary-select-methods '((nnmbox "")))
---------------------------
There is no ~/.gnus* files. Then i turn on debugging. Then i start
Gnus: M-x gnus. At some point of loading gnus, Emacs asks: "Revisit
the file literally?". If i answer yes, then Emacs `thinks' quite a
while (my mbox file is currently 13Mb, but this is not a problem ---
sometimes i had even bigger ones without problems). After `thinking',
gnus loads normally, and i can more-or-less normally read mail/news
[but there are usually some overestimations of numbers of articles in
my nnmbox groups which gnus reports], until i press `g' in the group
buffer to get new news/mail, in which case the situation repeats
(Emacs again asks that nasty question!). But if i press `n' on that
question, an error occurs. Here is another backtrace which i made
after fresh start of emacs, then turning on debuggning, starting gnus
and answering `n' to that question:
Signaling: (error "File already visited non-literally")
signal(error ("File already visited non-literally"))
error("File already visited non-literally")
find-file-noselect("/home/vvv/mbox" nil raw)
apply(find-file-noselect ("/home/vvv/mbox" nil raw))
nnheader-find-file-noselect("/home/vvv/mbox" nil raw)
nnmbox-read-mbox()
nnmbox-request-scan(nil "")
gnus-request-scan(nil (nnmbox ""))
gnus-read-active-file(nil nil)
gnus-setup-news(nil nil nil)
byte-code("\b\x0e
gnus-1(nil nil nil)
gnus(nil)
call-interactively(gnus)
execute-extended-command(nil)
* call-interactively(execute-extended-command)
May be, some contents of mbox makes Emacs to think that mbox is in
some particular coding system (there is some AI?). Maybe, gnus should
force a `literal' opening of mbox? But these are only is my guesses.
If i'll remove mbox and start from the new one, the error will
disappear (but i cannot start from fresh mbox right now; and this bug
should be corrected in any case). *Please* help! This is definitely a
bug of gnus, because it appears in a very clear situation (with that
primitive .emacs file).
Best regards, -- Vladimir.
next prev parent reply other threads:[~1998-10-01 5:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-29 20:29 bug? Vladimir Volovich
1998-10-01 5:15 ` Vladimir Volovich [this message]
1998-10-01 9:37 ` bug: coding system for mbox? Vladimir Volovich
1998-10-01 11:48 ` semi-pgnus? Steinar Bang
1998-10-01 22:04 ` semi-pgnus? Vladimir Volovich
1998-10-01 14:12 ` bug: coding system for mbox? Lars Magne Ingebrigtsen
1998-10-01 18:02 ` Vladimir Volovich
1998-10-01 22:57 ` Vladimir Volovich
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=m3k92k2785.fsf@vvv.vsu.ru \
--to=vvv@vvv.vsu.ru \
/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).