unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Jason Vas Dias <jason.vas.dias@ptt.ie>
Cc: emacs-devel@gnu.org, jasson.vas.dias@gmail.com,
	jason.vas.dias@pttireland.ie, Eli Zaretskii <eliz@gnu.org>,
	72126-done@debbugs.gnu.org
Subject: Bug#72126 fixed: v29.2 Java FontLock mode weirdness ?
Date: Mon, 22 Jul 2024 12:40:22 +0000	[thread overview]
Message-ID: <Zp5TNgUCYJIN4aFj@ACM> (raw)
In-Reply-To: <ZpQ3nPftg830WVrz@ACM>

Hello, Jason.

On Sun, Jul 14, 2024 at 20:39:56 +0000, Alan Mackenzie wrote:

[ .... ]

> 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 (thanks to the volunteer who does this).

So I'm now closing the bug.  If that turns out to be a mistake, please
get back to us, so that we can reopen it.

[ .... ]

> >   Thanks, Best Regards,
> >   Jason
  
-- 
Alan Mackenzie (Nuremberg, Germany).



  parent reply	other threads:[~2024-07-22 12:40 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   ` Alan Mackenzie [this message]
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
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=Zp5TNgUCYJIN4aFj@ACM \
    --to=acm@muc.de \
    --cc=72126-done@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jason.vas.dias@ptt.ie \
    --cc=jason.vas.dias@pttireland.ie \
    --cc=jasson.vas.dias@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 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).