From: Tim Cross <theophilusx@gmail.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: emacs-devel@gnu.org
Subject: Re: SOLVED: Re: How the long-lines "optimisation" breaks font locking.
Date: Sat, 06 Aug 2022 09:11:56 +1000 [thread overview]
Message-ID: <86wnbmjndk.fsf@gmail.com> (raw)
In-Reply-To: <87tu6qajvf.fsf@ucl.ac.uk>
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> On Friday, 5 Aug 2022 at 13:28, Eric S Fraga wrote:
>> I am having a few problems with the current Emacs including input
>> methods (none) and various undefined font-lock faces, having changed
>> *nothing* in my configuration.
>
> Okay, I have at least tracked down the font lock faces problem:
> font-lock-reference-face has been deleted as it had been marked obsolete
> for some time. Unfortunately, there are several packages out there in
> the wild still using it including ess, gnuplot-mode, and
> graphviz-dot-mode, both of which are crucial to my work. Hey hum. Time
> to edit and post issues where relevant.
>
> But I still have no input methods... is there an autoload missing in
> the build or init process maybe, as the relevant .el files are all
> there?
>
>
What (if any) arguments do you pass to configure?
next prev parent reply other threads:[~2022-08-05 23:11 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 18:39 How the long-lines "optimisation" breaks font locking Alan Mackenzie
2022-08-03 19:03 ` Lars Ingebrigtsen
2022-08-04 10:44 ` Alan Mackenzie
2022-08-04 12:54 ` Eli Zaretskii
2022-08-04 14:44 ` Alan Mackenzie
2022-08-04 14:52 ` Lars Ingebrigtsen
2022-08-04 15:22 ` Gregory Heytings
2022-08-05 1:23 ` Ihor Radchenko
2022-08-04 16:09 ` Eli Zaretskii
2022-08-05 10:56 ` Alan Mackenzie
2022-08-05 11:20 ` Eli Zaretskii
2022-08-05 13:04 ` Dmitry Gutov
2022-08-05 14:22 ` Eli Zaretskii
2022-08-05 14:29 ` Dmitry Gutov
2022-08-05 15:30 ` Eli Zaretskii
2022-08-05 19:50 ` Dmitry Gutov
2022-08-06 5:36 ` Eli Zaretskii
2022-08-06 10:54 ` Dmitry Gutov
2022-08-04 13:11 ` Eric S Fraga
2022-08-04 13:34 ` Po Lu
2022-08-04 14:38 ` Eric S Fraga
2022-08-04 16:16 ` SOLVED: " Eric S Fraga
2022-08-04 16:21 ` Eric S Fraga
2022-08-04 17:36 ` Stefan Kangas
2022-08-05 9:36 ` Eric S Fraga
2022-08-05 11:13 ` Eli Zaretskii
2022-08-05 12:28 ` Eric S Fraga
2022-08-05 13:40 ` Eric S Fraga
2022-08-05 23:11 ` Tim Cross [this message]
2022-08-05 23:23 ` Lars Ingebrigtsen
2022-08-08 11:51 ` Fraga, Eric
2022-08-03 19:15 ` Eli Zaretskii
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=86wnbmjndk.fsf@gmail.com \
--to=theophilusx@gmail.com \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-devel@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).