Gnus development mailing list
 help / color / mirror / Atom feed
From: Vladimir Volovich <vvv@vvv.vsu.ru>
Cc: ding@gnus.org
Subject: Re: MULE bites
Date: 16 Feb 1999 19:05:53 +0300	[thread overview]
Message-ID: <m3ogmucp0e.fsf@vvv.vsu.ru> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "16 Feb 1999 16:27:53 +0100"

[-- Attachment #1: Type: text/plain, Size: 1588 bytes --]

"KG" == Kai Grossjohann writes:

 KG> Okay, this is the first time I've been bitten by MULE (at least I
 KG> presume that's where the error comes from).  I nnoo'd a new
 KG> backend, inheriting most of the stuff from nnmbox.  I created a
 KG> server for this backend.  I added a message with a Latin-1
 KG> character.  Now, when typing `g' in the group buffer, I get asked
 KG> (two times, I've got two groups): Revisit file literally?

 KG> When I say yes, I get that dreaded \201 thingy.

 KG> What do I do now?

unfortunately, this seems to be a hard-to-fix bug in Emacs/MULE. I
also "suffer" from this problem: from time to time, when i receive
mails to my mbox which contain some binary characters, this leads to
brokenness of Gnus' dealing with my mbox. Each time pressing `g' in a
group buffer starts to take a LOT of time (with bug mbox size, such as
10MB and more); note that if the mbox does not contain those `broken'
messages with some bytes which confuse MULE (or gnus?), pressing `g'
takes much less than a second (if there are no new messages). And
also, in this case article numbering in group buffer reported by gnus
becomes broken (commonly overestimated by 1 or 2). Lars some time ago
made the following patch for files.el which "hides" the Emacs'
questions "Revisit file literally?", but this patch ODES NOT SOLVE THE
REAL PROBLEM: the above-mentioned symptoms are still valid; and they
are TRIGGERED by the presence in the mbox of some `broken' messages (i
have some examples and could send them). So, i'd be grateful to you if
you could report this problem to RMS.


[-- Attachment #2: Type: text/plain, Size: 566 bytes --]

--- /usr/share/emacs/20.3/lisp/files.el~	Fri Oct  2 14:27:51 1998
+++ /usr/share/emacs/20.3/lisp/files.el	Fri Oct  2 14:27:57 1998
@@ -928,8 +928,9 @@
 			   (buffer-name buf))))
 		       (with-current-buffer buf
 			 (revert-buffer t t)))))
-	    (when (not (eq rawfile (not (null find-file-literally))))
-	      (with-current-buffer buf
+	    (with-current-buffer buf
+	      (when (not (eq (not (null rawfile))
+			     (not (null find-file-literally))))
 		(if (buffer-modified-p)
 		    (if (y-or-n-p (if rawfile
 				      "Save file and revisit literally? "

[-- Attachment #3: Type: text/plain, Size: 27 bytes --]

Best regards, -- Vladimir.

  reply	other threads:[~1999-02-16 16:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-16 15:27 Kai.Grossjohann
1999-02-16 16:05 ` Vladimir Volovich [this message]
1999-02-19 16:22 ` Lars Magne Ingebrigtsen

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=m3ogmucp0e.fsf@vvv.vsu.ru \
    --to=vvv@vvv.vsu.ru \
    --cc=ding@gnus.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).