From: Stefan Kangas <stefan@marxist.se>
To: Drew Adams <drew.adams@oracle.com>
Cc: 51576@debbugs.gnu.org
Subject: bug#51576: 27.2; Bad error message for `defface' with no doc string
Date: Wed, 3 Nov 2021 15:29:44 -0700 [thread overview]
Message-ID: <CADwFkmk1yU3pA2tqRV_urXLgOEeqdtFe4_CJi5Ft3JHq6Z1Dgw@mail.gmail.com> (raw)
In-Reply-To: <SJ0PR10MB5488F27041DC936961E56BF7F38C9@SJ0PR10MB5488.namprd10.prod.outlook.com> (Drew Adams's message of "Wed, 3 Nov 2021 02:30:09 +0000")
tags 51576 + confirmed easy
found 51576 29.0.50
thanks
Drew Adams <drew.adams@oracle.com> writes:
> emacs -Q
>
> Eval this:
>
> (defface foo '((t :background "gray70" :inherit region))
> :group 'faces :type 'sexp)
>
> Instead of telling you the doc string is missing, the error message says
> this:
>
> Debugger entered--Lisp error: (error "Unknown keyword faces")
> signal(error ("Unknown keyword faces"))
> error("Unknown keyword %s" faces)
> custom-handle-keyword(foo faces :type custom-face)
> custom-handle-all-keywords(foo (faces :type sexp) custom-face)
> custom-declare-face(foo ((t :background "gray70" :inherit region)) :group faces :type sexp)
> eval-region(146 231 t #f(compiled-function (ignore) #<bytecode 0x2293dd9>)) ; Reading at buffer position 151
> elisp--eval-defun()
> eval-defun(nil)
> funcall-interactively(eval-defun nil)
> call-interactively(eval-defun nil nil)
> command-execute(eval-defun)
I can reproduce this on current master. I agree that it would be better
to say that the docstring is missing here.
next prev parent reply other threads:[~2021-11-03 22:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 2:30 bug#51576: 27.2; Bad error message for `defface' with no doc string Drew Adams
2021-11-03 2:36 ` Drew Adams
2021-11-03 22:29 ` Stefan Kangas [this message]
2021-11-04 18:23 ` Lars Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADwFkmk1yU3pA2tqRV_urXLgOEeqdtFe4_CJi5Ft3JHq6Z1Dgw@mail.gmail.com \
--to=stefan@marxist.se \
--cc=51576@debbugs.gnu.org \
--cc=drew.adams@oracle.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.