unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 55579@debbugs.gnu.org, juri@linkov.net
Subject: bug#55579: 29.0.50; Abbrevs not saved on exit anymore
Date: Wed, 25 May 2022 16:54:41 +0300	[thread overview]
Message-ID: <83k0a94t0e.fsf@gnu.org> (raw)
In-Reply-To: <87ilptert4.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed,  25 May 2022 14:10:31 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Juri Linkov <juri@linkov.net>,  55579@debbugs.gnu.org
> Date: Wed, 25 May 2022 14:10:31 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> BTW, I noticed that ~/.emacs.d/abbrev_defs
> >> is visited without font-locking.  Here's the fix:
> >
> > Won't that make loading abbrevs slower and more expensive?  that file
> > is normally not edited interactively, only if the user explicitly
> > wants to do so.  So why is font-lock in it important?
> 
> `read-abbrev-file' just uses `load' on the file, so the mode cookie
> doesn't do anything non-interactively.

Then let's have a comment where the cookie is written to explain
that it assumes 'load', and let's have another comment where we load
the file to explain why using another function should consider this
aspect.





  reply	other threads:[~2022-05-25 13:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-22 17:10 bug#55579: 29.0.50; Abbrevs not saved on exit anymore Juri Linkov
2022-05-23  7:46 ` Lars Ingebrigtsen
2022-05-24 18:42 ` Juri Linkov
2022-05-24 19:17   ` Lars Ingebrigtsen
2022-05-24 19:27   ` Eli Zaretskii
2022-05-25  5:51     ` Andreas Röhler
2022-05-25  6:37     ` Juri Linkov
2022-05-25 13:21       ` Eli Zaretskii
2022-05-25 17:34         ` Juri Linkov
2022-05-25 12:10     ` Lars Ingebrigtsen
2022-05-25 13:54       ` Eli Zaretskii [this message]
2022-05-27 10:21         ` Lars Ingebrigtsen

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=83k0a94t0e.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=55579@debbugs.gnu.org \
    --cc=juri@linkov.net \
    --cc=larsi@gnus.org \
    /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).