Stef, try setting log-message-ignore-labels and log-message-ignore-regexps to
nil.
that will ensure that all messages get logged.
ben
----- Original Message -----
From: "Stef Epardaud" <stef(a)lunatech.com>
To: <xemacs-beta(a)xemacs.org>
Sent: Wednesday, March 12, 2003 6:41 AM
Subject: something weird with paren-mode
Hi,
I've had this problem for ages. I feel stupid that everytime instead of
noting the error message and reporting it, I fire up my workaround
instantly.
It has to do with the paren-mode. I think I have a matching parent
showing a highlight, then I open a new file, using TAB abusively,
splitting the screen in two for completion, then either I open the file
or I give up, and I get back to my original file. This is where I get
the message about paren modifier quitting something. Result is that
every highlight of matching paren will remain on screen forever. Unless
I quickly paren-set-mode a couple times until back to my original mode.
That makes everything back to normal.
The error message is not shown in the message log, and I cannot seem to
be able to reproduce it although I'm confident that it happens every
week.
Sorry about the vagueness of the message, I'll try to remember to note
it down next time, but I was wondering if anyone experienced the same
problem?
--
# Stef Epardaud, # Teachers have potentially more power than military,
# Java Defeater # the former can teach us how to not need the latter.
# Earth # Lunatech Research,
# Solar System # soon we'll quit researching and start finding...