From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 55579@debbugs.gnu.org
Subject: bug#55579: 29.0.50; Abbrevs not saved on exit anymore
Date: Wed, 25 May 2022 20:34:53 +0300 [thread overview]
Message-ID: <86o7zlwt4a.fsf@mail.linkov.net> (raw)
In-Reply-To: <83o7zl4ujj.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 25 May 2022 16:21:36 +0300")
>> >> > Save abbrevs in ~/.emacs.d/abbrev_defs?
>> >>
>> >> 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?
>>
>> This is part of recent efforts to add modes to .emacs.d files.
>> So far we added the mode tag to ~/.emacs.d/bookmarks, ~/.emacs.d/tramp,
>> ~/.emacs.d/.emacs.desktop, ~/.emacs.d/network-security.data,
>> ~/.emacs.d/places, ~/.emacs.d/projects. But mode is still missing
>> in ~/.emacs.d/abbrev_defs and ~/.emacs.d/recentf.
>
> We don't need to do that for all of the files, only for files that are
> frequently (or always) visited or edited interactively by users. So
> I'm asking this question specifically for abbrev_defs, not for all the
> other files there: why do we need this, and how significant is the
> reason?
Of course, it's visited frequently. This is necessary to see
what abbreviations are defined.
next prev parent reply other threads:[~2022-05-25 17:34 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 [this message]
2022-05-25 12:10 ` Lars Ingebrigtsen
2022-05-25 13:54 ` Eli Zaretskii
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=86o7zlwt4a.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=55579@debbugs.gnu.org \
--cc=eliz@gnu.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).