From: Stefan Kangas <stefankangas@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>, Eli Zaretskii <eliz@gnu.org>
Cc: bjorn.bidar@thaodan.de, 68648@debbugs.gnu.org
Subject: bug#68648: 30.0.50; read-only-mode-hook's are not executed when buffer-read-only is t
Date: Sat, 3 Feb 2024 17:09:53 -0500 [thread overview]
Message-ID: <CADwFkm=OrEXkZUjBA_g4QDS1vCxcFDNR+p=cW7MLur_sKezBOQ@mail.gmail.com> (raw)
In-Reply-To: <jwvv8753441.fsf-monnier+emacs@gnu.org>
Stefan Monnier <monnier@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.
next prev parent reply other threads:[~2024-02-03 22:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <875xzma0hd.fsf@>
2024-01-22 9:00 ` bug#68648: 30.0.50; read-only-mode-hook's are not executed when buffer-read-only is t Eli Zaretskii
2024-01-23 13:47 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-23 13:47 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <874jf4nove.fsf@>
2024-01-23 18:23 ` Eli Zaretskii
2024-02-01 9:48 ` Eli Zaretskii
2024-02-01 14:17 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-01 14:58 ` Eli Zaretskii
2024-02-01 17:58 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-03 9:32 ` Eli Zaretskii
2024-02-03 16:28 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-03 22:09 ` Stefan Kangas [this message]
2024-02-10 8:37 ` Eli Zaretskii
2024-01-21 20:35 Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADwFkm=OrEXkZUjBA_g4QDS1vCxcFDNR+p=cW7MLur_sKezBOQ@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=68648@debbugs.gnu.org \
--cc=bjorn.bidar@thaodan.de \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).