From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Neal Sidhwaney Newsgroups: gmane.emacs.bugs Subject: bug#64824: 30.0.50; define-error not fontified in font-lock mode Date: Mon, 24 Jul 2023 15:28:14 -0400 Message-ID: References: <874jlugqbr.fsf@archlinux.mail-host-address-is-not-set> <83mszlsdpr.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000c3c7540601409f5a" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="4811"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 64824@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Jul 25 09:29:19 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 1qOCTu-00012e-RO for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 25 Jul 2023 09:29:18 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qOCTm-0007uj-K0; Tue, 25 Jul 2023 03:29:10 -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 1qOCTe-0007qW-Pr for bug-gnu-emacs@gnu.org; Tue, 25 Jul 2023 03:29:04 -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 1qOCTe-0006oy-Hk for bug-gnu-emacs@gnu.org; Tue, 25 Jul 2023 03:29:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1qOCTe-0001KT-Ap for bug-gnu-emacs@gnu.org; Tue, 25 Jul 2023 03:29:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Neal Sidhwaney Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 25 Jul 2023 07:29:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 64824 X-GNU-PR-Package: emacs Original-Received: via spool by 64824-submit@debbugs.gnu.org id=B64824.16902701295077 (code B ref 64824); Tue, 25 Jul 2023 07:29:02 +0000 Original-Received: (at 64824) by debbugs.gnu.org; 25 Jul 2023 07:28:49 +0000 Original-Received: from localhost ([127.0.0.1]:44549 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qOCTN-0001Jk-OV for submit@debbugs.gnu.org; Tue, 25 Jul 2023 03:28:49 -0400 Original-Received: from mail-ej1-x633.google.com ([2a00:1450:4864:20::633]:59618) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qO1El-0003ZN-Vz for 64824@debbugs.gnu.org; Mon, 24 Jul 2023 15:28:57 -0400 Original-Received: by mail-ej1-x633.google.com with SMTP id a640c23a62f3a-98dfb3f9af6so816623266b.2 for <64824@debbugs.gnu.org>; Mon, 24 Jul 2023 12:28:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1690226930; x=1690831730; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=tdj9bQLdxCg4z7k96EgprJ5FpN1+Gm7fE1zZjn+Z+BM=; b=gSLmF60P4h+NlUQlwBlbDrfs/sWe3ut6y8jPODwqheX1qcYkdW+zKlHaU8sJRfJtM6 zIEg2gdo30DEzjFyEp/6XkDH1bEzsqSWYEpj5rr8TrnE7OXSrxFFy6pZKQ/1zVAK6Ruw LwS9KGQ2YSfLiMJyTT3U9o4sePZqvM7ZJsr7esnFqMNz8JRP/OuJow9mdTZX+gsYKdx5 on3gokqPNDokgIeN1ZzWqrh481hS1KadCYdj6ZQS5eXkmzLCO38WlZOBtTJZ7AyBP4yM rTZF0HhPpDp4WfFU/HYLCnh+z5nXzSJHj1Jehdv2CVTwx2J1TDO1exNEOSkmwnFGBYGQ 16qQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690226930; x=1690831730; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=tdj9bQLdxCg4z7k96EgprJ5FpN1+Gm7fE1zZjn+Z+BM=; b=eGLXkaO/PxMmyaLyIRqbhR3YT0ZvYlY8tZwNrxyWdfvtVcGxZ9owf5YpbFyMiB8HpV XZjyey9hfnSqUaE3TQn4HK7DJU6eprDHkS0gbFOpZGohRInb03wDgSZKhMlkkNWSSiAl a9Y01kE5EBHCDgIBTDnLsArOPLo8CCoReGcgoFEt+PdfSM62wzgEpQbtg7A3Ra8uof4j HigLzAmwZpVwnS/Jm660x9esPq1adwSflXi0plO5AfNUrulKPJta9xo5CMSao31V7T4Q +nxn2DhKvXVrSfwE5zTcQArtJQExhSKfO14NKiLX1FkdbngXhBCZEv6iqn7Fw4eXzLMg A6RQ== X-Gm-Message-State: ABy/qLZ+HwD/h0NN3/0cbVTPc/VwSaIfx+PmQsZlibpX75PHKAprzxuD GauL2o8xpfWoVR6Q5+EQlSIP1ikyppaSqicTcMI= X-Google-Smtp-Source: APBJJlEzk/Ze5evQFnJZPC8ohEAPGRCE0hM5CO96zpjwg0mWlVZ/6WO3daPSmJl9Dz0V50jn2VlYSpsRsIeUSLbspP0= X-Received: by 2002:a17:906:51de:b0:993:d97f:ae06 with SMTP id v30-20020a17090651de00b00993d97fae06mr11262122ejk.13.1690226930204; Mon, 24 Jul 2023 12:28:50 -0700 (PDT) In-Reply-To: <83mszlsdpr.fsf@gnu.org> X-Mailman-Approved-At: Tue, 25 Jul 2023 03:28:41 -0400 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:266023 Archived-At: --000000000000c3c7540601409f5a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks! Sorry, forgot the patch in the first email =F0=9F=A4=A6=E2=80=8D=E2= =99=82=EF=B8=8F On Mon, Jul 24, 2023 at 8:19=E2=80=AFAM Eli Zaretskii wrote: > merge 64824 64823 > thanks > > > From: nealsid@gmail.com > > Date: Sun, 23 Jul 2023 19:28:56 -0400 > > > > In a buffer with emacs-lisp-mode active, 'define-error' is not fontifie= d > > by font-lock mode. The keyword should be listed somewhere around line > 360 in > > emacs-lisp/lisp-mode.el. > > > > Recipe: > > > > - Start emacs > > - Visit a file ending in .el > > - Type: (define-error 'new-error "this is a new error") > > - Wait for fontification to complete and notice it is not highlighted > > > > In lisp-mode.el, there is a comment about constructs being updated > > automatically from obarray, but I was not able to understand how this > > happens, and thought maybe the comment is referring to symbols created > > with those commands? > > Thanks I merged this with your original report, since it's the same > issue. > --000000000000c3c7540601409f5a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks! Sorry, forgot the patch in the first email =F0=9F= =A4=A6=E2=80=8D=E2=99=82=EF=B8=8F

On Mon, Jul 24, 2023 at 8:19=E2=80=AFAM El= i Zaretskii <eliz@gnu.org> wrote:=
merge 64824 64823
thanks

> From: nealsid@g= mail.com
> Date: Sun, 23 Jul 2023 19:28:56 -0400
>
> In a buffer with emacs-lisp-mode active, 'define-error' is not= fontified
> by font-lock mode.=C2=A0 The keyword should be listed somewhere around= line 360 in
> emacs-lisp/lisp-mode.el.
>
> Recipe:
>
> - Start emacs
> - Visit a file ending in .el
> - Type: (define-error 'new-error "this is a new error")<= br> > - Wait for fontification to complete and notice it is not highlighted<= br> >
> In lisp-mode.el, there is a comment about constructs being updated
> automatically from obarray, but I was not able to understand how this<= br> > happens, and thought maybe the comment is referring to symbols created=
> with those commands?

Thanks I merged this with your original report, since it's the same
issue.
--000000000000c3c7540601409f5a--