From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Mattias =?UTF-8?Q?Engdeg=C3=A5rd?= Newsgroups: gmane.emacs.bugs Subject: bug#67008: 30.0.50; Multiple major mode parents Date: Thu, 16 Nov 2023 12:07:58 +0100 Message-ID: <7717747E-42EB-445A-8487-822C0E932465@gmail.com> References: <445405AC-C0DA-4914-984E-B42671AB536D@gmail.com> <7C4E82A5-0F5A-4E04-B2BD-AD6DEC56A8C0@gmail.com> <2D8636AB-AB86-4FB5-BCCB-E10D0B9CD8C8@gmail.com> Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.15\)) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33837"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 67008@debbugs.gnu.org, Ikumi Keita , Yuan Fu , Dmitry Gutov To: Stefan Monnier Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Nov 16 12:09:21 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 1r3aFN-0008d4-AH for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 16 Nov 2023 12:09:21 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1r3aF7-0002yt-65; Thu, 16 Nov 2023 06:09:05 -0500 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 1r3aF4-0002yj-Sy for bug-gnu-emacs@gnu.org; Thu, 16 Nov 2023 06:09:02 -0500 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 1r3aF4-0003SM-KH for bug-gnu-emacs@gnu.org; Thu, 16 Nov 2023 06:09:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1r3aF3-00050f-Sg for bug-gnu-emacs@gnu.org; Thu, 16 Nov 2023 06:09:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Mattias =?UTF-8?Q?Engdeg=C3=A5rd?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 16 Nov 2023 11:09:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 67008 X-GNU-PR-Package: emacs Original-Received: via spool by 67008-submit@debbugs.gnu.org id=B67008.170013289019190 (code B ref 67008); Thu, 16 Nov 2023 11:09:01 +0000 Original-Received: (at 67008) by debbugs.gnu.org; 16 Nov 2023 11:08:10 +0000 Original-Received: from localhost ([127.0.0.1]:54573 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1r3aEE-0004zS-Ab for submit@debbugs.gnu.org; Thu, 16 Nov 2023 06:08:10 -0500 Original-Received: from mail-lf1-x129.google.com ([2a00:1450:4864:20::129]:60527) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1r3aEB-0004z0-9x for 67008@debbugs.gnu.org; Thu, 16 Nov 2023 06:08:08 -0500 Original-Received: by mail-lf1-x129.google.com with SMTP id 2adb3069b0e04-507962561adso975249e87.0 for <67008@debbugs.gnu.org>; Thu, 16 Nov 2023 03:08:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1700132881; x=1700737681; darn=debbugs.gnu.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:sender:from:to:cc:subject :date:message-id:reply-to; bh=NYoEnfrT96UmRodfCnmPGOhzLwUio7K2aNkVcpIvtoA=; b=ixP04oSUzNWDHAKda8cDcEH7rNUuee9ZDNLEEX/2jj3tcYwgE/O+FNU2VmrKhB5XZb SZd5Wuo3RjqjmhdynUmGyHlSDM3j/WCBxuEK2DAyZ0RkV/P4WZrLbVzrrzJtLJy5kgxQ PoJFQG+1SSdsLI/72X/+ZBvdU6jp/ypjBS50MAy711+fYmbQb8ZpcUXfzLU4ARTTIRKo y5xPNjMM2D3wNpPUuEgd6VGvPiyFSvcImHpjQvnmbjlciP97HMdYprocR0o99pxuOm+p 0F4vG9+izsDtDP7MpLkKSIHMwoMKxg+wLpcpcxHsyTGss4WCtJRXqx1pphS/PPbEzbbY ty7A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700132881; x=1700737681; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:sender:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=NYoEnfrT96UmRodfCnmPGOhzLwUio7K2aNkVcpIvtoA=; b=nhcl0WnnY9JHrdLH8tZ3aIkIKzuMldqp29AlM37re2D9xTMeTZ8jqOSpH06cBKXFfW bgzI2XR5cENbhUo9Efgxj49HqEb9ZAcPBZci1seLFjdzEnZyVjX67Lh0dfhdhXNxgzuG VsdM94AP/ActokbUOZ26IhNHZcSrcXxbpONGpk2yg4QePKTmmiPs8EVZJYUCw8B8zizD QfhNeUN6n31cfmr5g/h3Kp3tUgiL9Q/gdqBHOSCxAsDAIpnVbhzLa9GoaHFsFXD/mX8c bQxhDkjPy8c4u6Ep41En2VgEF+GYRUbMqahAS8cRC858qU3/r6HGAM2JMVMeR95dHyyd UHog== X-Gm-Message-State: AOJu0YyeIfxFYqCTASehl7IcVLhlvZpyckCsNpo4qy68nTGQyJbHNeBq tYcJgwvoNgd1qdZvySIY2IY= X-Google-Smtp-Source: AGHT+IHgnklNK84Bzq2hj7o8qkmMKLfUDGP0IBhq1mv4Vz1uZey4xd9bVtMRAhBjIS9rp5PlUoD5Hg== X-Received: by 2002:a19:7013:0:b0:505:8075:7c10 with SMTP id h19-20020a197013000000b0050580757c10mr10215351lfc.25.1700132881305; Thu, 16 Nov 2023 03:08:01 -0800 (PST) Original-Received: from smtpclient.apple (c188-150-165-235.bredband.tele2.se. [188.150.165.235]) by smtp.gmail.com with ESMTPSA id c20-20020a056512075400b005068e7a2e7dsm1921318lfs.77.2023.11.16.03.08.00 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 16 Nov 2023 03:08:00 -0800 (PST) In-Reply-To: X-Mailer: Apple Mail (2.3654.120.0.1.15) 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:274451 Archived-At: > Yes we strictly obey the vertical edges (and call `error-function` = when > that's not an option) and we use the horizontal edges when there's > a choice. Yes, but `merge-ordered-lists` doesn't distinguish between vertical and = horizontal edges in any way, does it? We only get a consistent = (monotonic) result if the input is ordered correctly. In that respect `merge-ordered-lists` is just half an algorithm. We = could add the other half but presumably this wouldn't be a good fit in = places where the function is currently used? The other half might be something like: compute the linear order for = each parent in sequence, then add the partial order (NODE = PARENT1...PARENTn). The documentation text > The order of the (sub)lists determines the final order in those cases = where > the order within the sublists does not impose a unique choice. > Equality of elements is tested with `eql'. could perhaps be written more precisely to say that when the constraints = do not impose a relative order between elements (not sublists), they are = ordered by their occurrence in the input. `merge-ordered-lists` should also have the left-to-right property that (merge-ordered-lists (append X Y)) =3D (merge-ordered-lists (cons (merge-ordered-lists X) Y)) although I haven't verified this.