[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#22272: 24.5; nonfunctional Emacs with a bad global mode (post-comman
From: |
Bruno BARBIER |
Subject: |
bug#22272: 24.5; nonfunctional Emacs with a bad global mode (post-command-hook). |
Date: |
Thu, 31 Dec 2015 07:40:19 +0100 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Wed, Dec 30, 2015 at 09:28:31PM +0100, Michael Heerdegen wrote:
> Bruno BARBIER <brubar.cs@gmail.com> writes:
>
> > 1. the error is not silenced,
> >
> > 2. and the function is not removed.
> >
> > Thus, the error is constantly raised rendering Emacs
> > nonfunctional. That's why I had to ask the OS to kill my Emacs.
> >
> > So, I'm saying Emacs could be slightly improved by following what the
> > documentation says.
> >
> > Am I wrong ?
>
> Emacs behaves as documented, but the situation is more complicated as
> you expect - See the code `define-globalized-minor-mode':
>
> Turning on a globalized minor mode pushes a function to
> change-major-mode-hook that adds a function to post-command-hook - and
> that's the one that fails. So the cited behavior of Emacs removing the
> erroneous function from post-command-hook doesn't solve the problem
> permanently.
Ok. I see. Not that simple indeed and I was wrong: the error is
silenced and the function removed (but `change-major-mode-hook' pushes
it back into `post-command-hook' as instructed by
`define-globalized-minor-mode').
The simplest solution is probably to use a spare Emacs when
developping a new global mode and to catch errors in it; that makes
sense.
I guess this non bug should be closed. Sorry for the noise.
Thanks Eli and Michael for your prompt reply and your time.
Bruno.
>
> Michael.
>