unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Lars Ingebrigtsen <larsi@gnus.org>
Cc: "51577@debbugs.gnu.org" <51577@debbugs.gnu.org>
Subject: bug#51577: [External] : Re: bug#51577: 27.2; Regression: reproducible hang with face functions
Date: Thu, 4 Nov 2021 19:21:27 +0000	[thread overview]
Message-ID: <SJ0PR10MB548824CCE75FD28FCB000A37F38D9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <83y263eod4.fsf@gnu.org>

> As for detecting loops: it could be tricky.  It is easy enough to
> detect simple loops such as the one in this case, where a face
> inherits directly from itself, and the value of the :inherit attribute
> is the symbol of a face.  But inheritance loops could be less simple:
> a face could inherit from itself indirectly, and the value of the
> attribute could be a list, not a named face.  Detecting loops in those
> cases would require recording face specs/names we already saw in some
> list, and each time we get an :inherit attribute, check if its value
> is already in the list.  Is that worth our while, if the result will
> be a silent error message in *Messages*?

Yes, nested inherits are more complicated.

Whether some attempt is made in that regard
could maybe be a wishlist request.

Let's not let ideal become the enemy of good,
here.

I'd be happy just removing the regression, i.e.,
returning to the behavior prior to Emacs 27
(in this regard - I don't mean just reverting
code; how to remove the regression is up to you).

IOW, allow a face `foo' to have (and ignore) an
`:inherit foo' in its face spec.

Clearly, somehow Emacs 26 tolerated such simple
self-inheritance (as a no-op).  Whether it did
so in the right way or not, in terms of design
or implementation, I don't know.





  reply	other threads:[~2021-11-04 19:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-03  2:44 bug#51577: 27.2; Regression: reproducible hang with face functions Drew Adams
2021-11-03 17:10 ` Eli Zaretskii
2021-11-03 18:58   ` bug#51577: [External] : " Drew Adams
2021-11-03 19:43     ` Eli Zaretskii
2021-11-04 18:15       ` Lars Ingebrigtsen
2021-11-04 18:48         ` martin rudalics
2021-11-04 18:50           ` Lars Ingebrigtsen
2021-11-04 19:32           ` Eli Zaretskii
2021-11-04 19:01         ` Eli Zaretskii
2021-11-04 19:21           ` Drew Adams [this message]
2021-11-04 22:56           ` Lars Ingebrigtsen
2021-11-05  2:41             ` bug#51577: [External] : " Drew Adams
2021-11-05  7:32               ` Eli Zaretskii
2021-11-05  7:19             ` Eli Zaretskii
2021-11-05 13:24               ` Lars Ingebrigtsen
2021-11-05 14:22                 ` Eli Zaretskii
2021-11-06  0:39                   ` 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

  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=SJ0PR10MB548824CCE75FD28FCB000A37F38D9@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=51577@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.org \
    /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).