From: Alan Mackenzie <acm@muc.de>
To: Jason Vas Dias <jason.vas.dias@ptt.ie>, jason.vas.dias@gmail.com
Cc: 72126@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>,
jason.vas.dias@pttireland.ie, emacs-devel@gnu.org, acm@muc.de
Subject: Re: bug#72126: closed (Bug#72126 fixed: v29.2 Java FontLock mode weirdness ?)
Date: Fri, 26 Jul 2024 16:00:48 +0000 [thread overview]
Message-ID: <ZqPIMKavQXyKm8zS@ACM> (raw)
In-Reply-To: <hhle1o5lo2.fsf@ptt.ie>
[-- Attachment #1: Type: text/plain, Size: 2201 bytes --]
Hello, Jason.
On Fri, Jul 26, 2024 at 14:26:37 +0100, Jason Vas Dias wrote:
> Good day Alan, Eli, all -
> Thank you for submitting a patch for this - as you stated :
> > Anyhow, here's the patch. Please apply it to
> > ..../lisp/progmodes/cc-engine.el in your Emacs directory, and then byte
> > compile the patched file, then load it (or start Emacs afresh). Please
> > test out the patched CC Mode with your real Java code, and confirm to me
> > that the bug has indeed been fixed. If you want any help with the
> > patching or byte compilation, feel free to send me private email.
> > I'm taking it that the patch works OK. I've committed it to the
> > emacs-30 release branch, from where it will find it way to the master
> > branch in the next few days
> I'd very much like to test your patch, ie. get an Emacs which fixes
> this problem, which is most annoying when editing large amounts of Java.
> But I could find no attached patch in any of your emails to me or on the bug
> report.
The patch was actually inline in my email from 2024-07-14 rather than
being an attached file. It is easier to read and comment on patches
this way unless they are big. Normally, patch is good (in fact,
astoundingly good) at ignoring irrelevant text, so all you need to do is
save the email to a file ~/foo.patch, followed by
$ cd .../lisp/progmodes
$ patch < ~/foo.patch
.. However, I'm attaching the patch to this mail again, anyway.
> Please could you send me either :
> A) The patch, against Emacs 30 (devel branch) -
> I can backport to v29.4 version
Will do.
> or
> B) A link to the correct GIT repo, and a Commit Reference ID - again,
> I can backport to v29.4
The commit to the emacs-30 branch was:
commit caf7426f0ca280b7cf40736e595cad8f7361152f (HEAD -> emacs-30)
Author: Alan Mackenzie <acm@muc.de>
Date: Mon Jul 22 12:24:43 2024 +0000
FIx spurious fontification of variable in Java Mode
> or
> C) The complete cc-engine.el from v29.4 with patch applied.
> On receipt, I will test and let you know the results.
Thanks!
> Thank You & Best Regards,
> Jason
--
Alan Mackenzie (Nuremberg, Germany).
[-- Attachment #2: diff.20240714.diff --]
[-- Type: text/plain, Size: 736 bytes --]
diff -r aba0055b21e4 cc-engine.el
--- a/cc-engine.el Mon Jul 01 20:21:18 2024 +0000
+++ b/cc-engine.el Sun Jul 14 20:21:48 2024 +0000
@@ -8794,6 +8794,7 @@
;; This function might do hidden buffer changes.
(let ((start (point))
+ (old-record-type-identifiers c-record-type-identifiers)
(old-found-types (copy-hash-table c-found-types))
;; If `c-record-type-identifiers' is set then activate
;; recording of any found types that constitute an argument in
@@ -8830,7 +8831,8 @@
(nconc c-record-found-types c-record-type-identifiers)))
t)
- (setq c-found-types old-found-types)
+ (setq c-record-type-identifiers old-record-type-identifiers
+ c-found-types old-found-types)
(goto-char start)
nil))))
next prev parent reply other threads:[~2024-07-26 16:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-14 15:33 v29.2 Java FontLock mode weirdness ? Jason Vas Dias
2024-07-14 20:39 ` Alan Mackenzie
2024-07-15 2:24 ` Eli Zaretskii
2024-07-15 13:37 ` v29.4: Anomalous Highlighting in "Java//l Abbrev" (java-mode) Jason Vas Dias
2024-07-22 12:40 ` Bug#72126 fixed: v29.2 Java FontLock mode weirdness ? Alan Mackenzie
2024-07-26 13:26 ` bug#72126: closed (Bug#72126 fixed: v29.2 Java FontLock mode weirdness ?) Jason Vas Dias
2024-07-26 16:00 ` Alan Mackenzie [this message]
2024-07-27 0:52 ` Jason Vas Dias
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=ZqPIMKavQXyKm8zS@ACM \
--to=acm@muc.de \
--cc=72126@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jason.vas.dias@gmail.com \
--cc=jason.vas.dias@ptt.ie \
--cc=jason.vas.dias@pttireland.ie \
/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).