From mboxrd@z Thu Jan  1 00:00:00 1970
Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail
From: Eli Zaretskii <eliz@gnu.org>
Newsgroups: gmane.emacs.devel
Subject: Re: Fwd: v29.2 Java FontLock mode weirdness ?
Date: Sun, 14 Jul 2024 20:40:06 +0300
Message-ID: <86y163j2ix.fsf@gnu.org>
References: <hhplrgkmro.fsf@ptt.ie>
 <CALyZvKwccvDn0wVu9iczBBGsjLOhryLtt1ZvuFh2rYqBt5wwCA@mail.gmail.com>
Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214";
	logging-data="16599"; mail-complaints-to="usenet@ciao.gmane.io"
Cc: emacs-devel@gnu.org
To: Jason Vas Dias <jason.vas.dias@gmail.com>
Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Jul 14 19:41:23 2024
Return-path: <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>
Envelope-to: ged-emacs-devel@m.gmane-mx.org
Original-Received: from lists.gnu.org ([209.51.188.17])
	by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>)
	id 1sT3Du-00044P-IL
	for ged-emacs-devel@m.gmane-mx.org; Sun, 14 Jul 2024 19:41:22 +0200
Original-Received: from localhost ([::1] helo=lists1p.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.90_1)
	(envelope-from <emacs-devel-bounces@gnu.org>)
	id 1sT3DS-0002pd-NY; Sun, 14 Jul 2024 13:40:55 -0400
Original-Received: from eggs.gnu.org ([2001:470:142:3::10])
 by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <eliz@gnu.org>) id 1sT3DJ-0002pA-62
 for emacs-devel@gnu.org; Sun, 14 Jul 2024 13:40:45 -0400
Original-Received: from fencepost.gnu.org ([2001:470:142:3::e])
 by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <eliz@gnu.org>)
 id 1sT3DI-0001yE-PD; Sun, 14 Jul 2024 13:40:44 -0400
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org;
 s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date:
 mime-version; bh=/HOCOksESyXh9RNf3DiRksrDW2gsKKCUuYtWGA6kzJk=; b=B44VnSSBHmQh
 tDzfpNDUyKEI/Mi160OCSFUsKs/J3vzyB/4g6ANe0JBz5rfNgeReG1Qx2iq8MPAZ0zMBnDSQrhe/q
 IxTZXErkiRin/i7i4IFRyiaPs85tsZ1aKuyIp+XXzQcprKjs4ZNMm7TpEh3XH+im/XSG6Foul0Cgn
 k/qR6C3N1W73RLsO9iG8014HbZRxB+D7dWq4pf+l6RoUhopSA0LquaSrZNvJ5JX+MJfRqzWzXMVo6
 c4xaOnO8aOoYfAkRNWvY+riS97DnFcLPIS13OPDbI+Uf8AgpCVyTbAS1KnlZgh196BZnBBe4B/3b/
 IEpReyEk8HC7ofjgrYGp/Q==;
In-Reply-To: <CALyZvKwccvDn0wVu9iczBBGsjLOhryLtt1ZvuFh2rYqBt5wwCA@mail.gmail.com>
 (message from Jason Vas Dias on Sun, 14 Jul 2024 16:39:24 +0100)
X-BeenThere: emacs-devel@gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Emacs development discussions." <emacs-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-devel>,
 <mailto:emacs-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/emacs-devel>
List-Post: <mailto:emacs-devel@gnu.org>
List-Help: <mailto:emacs-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-devel>,
 <mailto:emacs-devel-request@gnu.org?subject=subscribe>
Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org
Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org
Xref: news.gmane.io gmane.emacs.devel:321650
Archived-At: <http://permalink.gmane.org/gmane.emacs.devel/321650>

> From: Jason Vas Dias <jason.vas.dias@gmail.com>
> Date: Sun, 14 Jul 2024 16:39:24 +0100
> Cc: Jason Vas Dias <jason.vas.dias@ptt.ie>,
>  Jason Vas Dias <jason.vas.dias@pttireland.ie>
> 
>     Could anyone please enlighten me as to why, in enclosed Screenshot
>     of Emacs 29.2, running under Fedora 40 / XFce4 on x86_64, in Java,
>     the identifier after '>' in an 'if' clause is being specially highlighted ,
>     but not one after '>=' ? ie. 'bursttime_end' identifier is shown in
>     green bold only when after a '>' character, not when after '>=' .
> 
>     It looks like a bug to me, if only a niggle. Why doesn't this occur
>     in C font-lock mode ?

Please submit a bug report about this with all the details, and the
relevant developer(s) will investigate.

Thanks.