GNU bug report logs - #68648
30.0.50; read-only-mode-hook's are not executed when buffer-read-only is t

Previous Next

Full log

Message #46 received at 68648-done <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Kangas <stefankangas <at> gmail.com>
Cc: bjorn.bidar <at> thaodan.de, monnier <at> iro.umontreal.ca,
 68648-done <at> debbugs.gnu.org
Subject: Re: bug#68648: 30.0.50; read-only-mode-hook's are not executed when
 buffer-read-only is t
Date: Sat, 10 Feb 2024 10:37:02 +0200

> From: Stefan Kangas <stefankangas <at> gmail.com>
> Date: Sat, 3 Feb 2024 17:09:53 -0500
> Cc: bjorn.bidar <at> thaodan.de, 68648 <at> debbugs.gnu.org
> 
> Stefan Monnier <monnier <at> iro.umontreal.ca> writes:
> 
> >> On second thought, would it be okay to just call the mode hook where
> >> we set buffer-read-only in after-find-file?
> >
> > It's probably an acceptable middle ground until someone goes through the
> > trouble of sorting out how to make the code call `read-only-mode`.
> > Even better if the `run-hooks` is accompanied with a FIXME explaining
> > that :-)
> 
> Makes sense to me.

Now done on master, let's see what this breaks.

Closing.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.