all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: k3tu0isui@gmail.com
Cc: 45747@debbugs.gnu.org
Subject: bug#45747: 27.1; mercury-mode font lock bug
Date: Sun, 10 Jan 2021 14:38:14 +0100	[thread overview]
Message-ID: <87r1msud2x.fsf@gnus.org> (raw)
In-Reply-To: <20210110132824.h5m5mglfx23hrch7@sildranDT.localdomain> (k3tu0isui@gmail.com's message of "Sun, 10 Jan 2021 18:58:24 +0530")

k3tu0isui@gmail.com writes:

> Maybe prolog-mode-variables has already been called, but maybe due to
> (setq-local prolog-system 'mercury) not being set, some variables like
> prolog-determinism-specifiers-i and prolog-types-i are not being set
> to mercury values. So quite a bit of keywords are ignored when
> syntax-highlighting happens.

Ah, I missed that `prolog-find-value-by-system' (called by that
function) depended on `prolog-system', so I think your patch is correct,
and I've now applied it to Emacs 28.  (With the `derived-mode-p' tweak.)

This change was small enough to apply without assigning copyright to the
FSF, but for future patches you want to submit, it might make sense to
get the paperwork started now, so that subsequent patches can be applied
speedily. Would you be willing to sign such paperwork?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2021-01-10 13:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-09 13:22 bug#45747: 27.1; mercury-mode font lock bug k3tu0isui
2021-01-09 15:29 ` bug#45747: [PATCH] mercury-mode font lock fix k3tu0isui
2021-01-10 12:51   ` bug#45747: 27.1; mercury-mode font lock bug Lars Ingebrigtsen
2021-01-10 13:28     ` k3tu0isui
2021-01-10 13:38       ` Lars Ingebrigtsen [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r1msud2x.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=45747@debbugs.gnu.org \
    --cc=k3tu0isui@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.