MULE bites

MULE bites

[Kai.Grossjohann]

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

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

What do I do now?

kai
-- 
I like _\bb_\bo_\bt_\bh kinds of music.

Re: MULE bites

[Vladimir Volovich]

[-- 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.

Re: MULE bites

[Lars Magne Ingebrigtsen]

Kai.Grossjohann@CS.Uni-Dortmund.DE writes:

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

It's a bug somewhere in nnmbox, I think.  Well, nnmbox probably fails
to grok some Mule stuff (like Vladimir said), and I have looked into
it some, but some fresh eyes would probably be very helpful.  Could
you take a look at the problem as well?

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen