From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.bugs Subject: bug#65567: Uh, invalid. Date: Sun, 27 Aug 2023 16:20:59 +0200 Message-ID: <87il90in1w.fsf@fencepost.gnu.org> References: <87msycinsg.fsf@fencepost.gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="588"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) To: 65567@debbugs.gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun Aug 27 16:22:13 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@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 ) id 1qaGeZ-000AVm-Qn for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 27 Aug 2023 16:22:12 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qaGeN-0002qN-BF; Sun, 27 Aug 2023 10:21:59 -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 ) id 1qaGeL-0002o7-Cn for bug-gnu-emacs@gnu.org; Sun, 27 Aug 2023 10:21:57 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1qaGeL-0005La-4W for bug-gnu-emacs@gnu.org; Sun, 27 Aug 2023 10:21:57 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1qaGeQ-00023N-Hx for bug-gnu-emacs@gnu.org; Sun, 27 Aug 2023 10:22:02 -0400 X-Loop: help-debbugs@gnu.org In-Reply-To: <87msycinsg.fsf@fencepost.gnu.org> Resent-From: David Kastrup Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 27 Aug 2023 14:22:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 65567 X-GNU-PR-Package: emacs Original-Received: via spool by 65567-submit@debbugs.gnu.org id=B65567.16931460837839 (code B ref 65567); Sun, 27 Aug 2023 14:22:02 +0000 Original-Received: (at 65567) by debbugs.gnu.org; 27 Aug 2023 14:21:23 +0000 Original-Received: from localhost ([127.0.0.1]:45926 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qaGdn-00022N-HE for submit@debbugs.gnu.org; Sun, 27 Aug 2023 10:21:23 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:49454) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qaGdi-000227-Aq for 65567@debbugs.gnu.org; Sun, 27 Aug 2023 10:21:21 -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 ) id 1qaGdW-0005DJ-Re for 65567@debbugs.gnu.org; Sun, 27 Aug 2023 10:21:07 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-Version:Date:Subject:To:From:in-reply-to: references; bh=DAWW54sEHSzspBMIkjohuM3uCBfKBufdhJu9Gvlw/pY=; b=ChLv2I5mcgvdEz uEZUcE2HHgD1YUx+J/apvG5370fMMGF96wiEOSSWduQRGL7+nzt3wwRvXsp7iMplNeIFhoqA8gq3+ Y6WyveQQMop9W2k1SNwyvnyj2EgK5j5L2LJCWvfstQ6QpT5wQTNVCH8g9vM5faA+pMjLq3QKCo6sk WTXfMLCNzUh+nrB6UJOSsdUj+AFmAbDKp3dB/75xDZUmdV0ji0/4rlC8HQqD/wEYKbzePLH/N7sRg HQKFue/yu1khlBOckP4UAFraZvHHCqU5JK6qkBuv8oLZ4Is0E46Qb0okPX7HAxYkD5tIbls6pQl/3 Cwg1siCQaH3/3cc72Ufg==; X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:268555 Archived-At: It turns out that this bug is actually a result of an outdated lilypond-font-lock.el which has been fixed upstream in 22-05-2023. Sorry for the noise. -- David Kastrup