From debbugs-submit-bounces@debbugs.gnu.org Fri Nov 26 10:24:32 2021 Received: (at submit) by debbugs.gnu.org; 26 Nov 2021 15:24:32 +0000 Received: from localhost ([127.0.0.1]:60366 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mqd5U-0000ep-CO for submit@debbugs.gnu.org; Fri, 26 Nov 2021 10:24:32 -0500 Received: from lists.gnu.org ([209.51.188.17]:41178) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mqd5T-0000ei-63 for submit@debbugs.gnu.org; Fri, 26 Nov 2021 10:24:31 -0500 Received: from eggs.gnu.org ([209.51.188.92]:47602) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mqd5T-0001e7-2P for bug-gnu-emacs@gnu.org; Fri, 26 Nov 2021 10:24:31 -0500 Received: from mail-pf1-f173.google.com ([209.85.210.173]:39640) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1mqd5Q-0002qf-PI for bug-gnu-emacs@gnu.org; Fri, 26 Nov 2021 10:24:30 -0500 Received: by mail-pf1-f173.google.com with SMTP id i12so9280820pfd.6 for ; Fri, 26 Nov 2021 07:24:27 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=A+Dvt1fB6TmHhcljPnkL8hwhwX7ZMo03JXPxhvpOzW4=; b=UGsptF4KlZEneCr/lqcOT7EmthCWtOuoWYVkCnbiSiwHFl9351/cy9ncRPJSGAUU4Q rQqNkDhgiUZSMD4XxxZ9c/Zg+4c22ZMluXiKFem46NMhFt2kx2he+E7v7AIgGpyCQv97 JsncCjpvT73Bmyml0ZvVqb6m69SQBOWawGVce2eksIGcwO7uqgY1Qmi93jjMTaQT0FBw s1Onp4bWuSpoxu2VNOwmGOgDsa3/IEaSJ3IGZ8Yz2atpXwLCswOtGXWH03YW2yeyDjW9 qJ/WE9PGZF6W0Shwsq91lWtQnrR0NoZ04fHDOeidr4hUJl4bbGP4CRX3b+KT6vK7NhQt nmjw== X-Gm-Message-State: AOAM531MVaW12FJC5hos+6G4Y229m/nm6yFEXYqHgp8LLPKukXU3+qdH +lUFHbhmYJm5XMgTwnkM6EDPyz6I58pNXPYq8LvEkDzlEKw= X-Google-Smtp-Source: ABdhPJwf0YtqU8gL7RvwvhoLgZBz6npqKiGb5x7TiCxMcKCjJsRELJ9cpomwbubibfEPQyUROoXpUNdOJMadkxnNtGg= X-Received: by 2002:a63:eb47:: with SMTP id b7mr7770721pgk.591.1637940266395; Fri, 26 Nov 2021 07:24:26 -0800 (PST) MIME-Version: 1.0 From: Stefan Kangas Date: Fri, 26 Nov 2021 16:24:15 +0100 Message-ID: Subject: Problematic characters in info node names To: bug-gnu-emacs@gnu.org Content-Type: text/plain; charset="UTF-8" Received-SPF: pass client-ip=209.85.210.173; envelope-from=stefankangas@gmail.com; helo=mail-pf1-f173.google.com X-Spam_score_int: -13 X-Spam_score: -1.4 X-Spam_bar: - X-Spam_report: (-1.4 / 5.0 requ) BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-Spam-Score: -0.8 (/) X-Debbugs-Envelope-To: submit X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.8 (-) admin/release-process says: ** Manuals Check for node names using problematic characters: find doc -name '*.texi' -exec grep '^@node[^,]*[:.()]' {} + Sadly makeinfo does not warn about such characters. Running that gives me some matches: doc/misc/modus-themes.texi:@node Advanced customization (do-it-yourself) doc/misc/modus-themes.texi:@node Per-theme customization settings (DIY) doc/misc/modus-themes.texi:@node Case-by-case face specs using the themes' palette (DIY) doc/misc/modus-themes.texi:@node Face specs at scale using the themes' palette (DIY) doc/misc/modus-themes.texi:@node Remap face with local value (DIY) doc/misc/modus-themes.texi:@node Cycle through arbitrary colors (DIY) doc/misc/modus-themes.texi:@node Override colors (DIY) doc/misc/modus-themes.texi:@node Override color saturation (DIY) doc/misc/modus-themes.texi:@node Font configurations for Org and others (DIY) doc/misc/modus-themes.texi:@node Configure bold and italic faces (DIY) doc/misc/modus-themes.texi:@node Custom Org user faces (DIY) doc/misc/modus-themes.texi:@node Update Org block delimiter fontification (DIY) doc/misc/modus-themes.texi:@node Measure color contrast (DIY) doc/misc/modus-themes.texi:@node Load theme depending on time of day (DIY) doc/misc/modus-themes.texi:@node Backdrop for pdf-tools (DIY) doc/misc/modus-themes.texi:@node Decrease mode line height (DIY) doc/misc/modus-themes.texi:@node A theme-agnostic hook for theme loading (DIY) doc/misc/modus-themes.texi:@node Note on EWW and Elfeed fonts (SHR fonts) doc/misc/modus-themes.texi:@node Frequently Asked Questions (FAQ) doc/misc/org.texi:@node Hooks (2) However, there are no instructions for what to do about these cases. From debbugs-submit-bounces@debbugs.gnu.org Fri Nov 26 11:26:35 2021 Received: (at 52126) by debbugs.gnu.org; 26 Nov 2021 16:26:35 +0000 Received: from localhost ([127.0.0.1]:60466 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mqe3O-0002Lr-Ax for submit@debbugs.gnu.org; Fri, 26 Nov 2021 11:26:35 -0500 Received: from eggs.gnu.org ([209.51.188.92]:33496) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mqe3M-0002Lc-Aa for 52126@debbugs.gnu.org; Fri, 26 Nov 2021 11:26:24 -0500 Received: from [2001:470:142:3::e] (port=60406 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mqe3G-0002Xv-Sj; Fri, 26 Nov 2021 11:26:18 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=oKveWg0T2BZ3RssFjrkikU/Gedr8WdSXJsYkJB5jt7M=; b=C18dViWyBYdb m1xq+AYHsj+lin/y1LhW5MjruwEac7KVUA8zp70Ob/3QziqPD68oDfQVKxNynTyxcM1gdI5hyAdd3 743AGJs9ehJsaJ1tcDVPhPWC8BNghvHigNEv0vdL4Lj8Hcz7mshglBFtykRSvQZx737CJghzYSriq Cwx8DlJ5DXVJYX/8IDSfixENPxQ4BFT4725UsQYrjAuR8XV3JMCDi3sZFh14S3S0lDqIKcQ/n4TI/ ZEKCrQAGqjG+lYiRkM73eMPBmjsWJHNwJOrOdzrWAc6Nek+l+SGfYrwSum43Q6iWo44iM10cdUmH9 6pm+LNNGEGwpzC2lIW/X1A==; Received: from [87.69.77.57] (port=3971 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mqe3G-0004X9-K6; Fri, 26 Nov 2021 11:26:18 -0500 Date: Fri, 26 Nov 2021 18:26:23 +0200 Message-Id: <834k7y3mts.fsf@gnu.org> From: Eli Zaretskii To: Stefan Kangas In-Reply-To: (message from Stefan Kangas on Fri, 26 Nov 2021 16:24:15 +0100) Subject: Re: bug#52126: Problematic characters in info node names References: X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 52126 Cc: 52126@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) > From: Stefan Kangas > Date: Fri, 26 Nov 2021 16:24:15 +0100 > > admin/release-process says: > > ** Manuals > Check for node names using problematic characters: > find doc -name '*.texi' -exec grep '^@node[^,]*[:.()]' {} + > Sadly makeinfo does not warn about such characters. > > Running that gives me some matches: Please report to the respective developers, but other than that, we don't care too much. It isn't a grave problem, and in practice slmost never causes any trouble. > However, there are no instructions for what to do about these cases. There cannot be any instructions, since the manual authors should rewrite the relevant parts not to use those characters, if possible. Thanks. From debbugs-submit-bounces@debbugs.gnu.org Mon Nov 29 11:03:18 2021 Received: (at 52126) by debbugs.gnu.org; 29 Nov 2021 16:03:18 +0000 Received: from localhost ([127.0.0.1]:39071 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mrj7d-0005lz-Tt for submit@debbugs.gnu.org; Mon, 29 Nov 2021 11:03:18 -0500 Received: from quimby.gnus.org ([95.216.78.240]:59710) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mrj7b-0005le-Lo for 52126@debbugs.gnu.org; Mon, 29 Nov 2021 11:03:16 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date: References:Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=nIa6p7GtMkjV2oZMpMdvOQlpx4glVz6nw7KGVyeouzo=; b=QVQe6sgJVuuUqy1mz0ih2ndehr ipagloPAJXRyny5rcfptsVCwx8jTfyL9WOR0Rs3mkWyftPNTrtNhzWiEmSoLAA+rlhBEcag0Rqihy NKWFLyk9qAm4hkqwfJ5TAoqJwwPWA7YfyVXrq7XNnqN8/suHy/6MuofbfKbhMBj7j+hc=; Received: from [84.212.220.105] (helo=xo) by quimby.gnus.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mrj7R-0005xk-AD; Mon, 29 Nov 2021 17:03:07 +0100 From: Lars Ingebrigtsen To: Stefan Kangas Subject: Re: bug#52126: Problematic characters in info node names References: X-Now-Playing: Mia Doi Todd's _Music Life_: "Wainiha Valley (feat. Laraaji)" Date: Mon, 29 Nov 2021 17:03:03 +0100 In-Reply-To: (Stefan Kangas's message of "Fri, 26 Nov 2021 16:24:15 +0100") Message-ID: <871r2zueyw.fsf@gnus.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Spam-Report: Spam detection software, running on the system "quimby.gnus.org", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see @@CONTACT_ADDRESS@@ for details. Content preview: Stefan Kangas writes: > ** Manuals > Check for node names using problematic characters: > find doc -name '*.texi' -exec grep '^@node[^, ]*[:.()]' {} + > Sadly makeinfo does not warn about such characters. > > Running that g [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 52126 Cc: 52126@debbugs.gnu.org, Protesilaos Stavrou , Kyle Meyer X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) Stefan Kangas writes: > ** Manuals > Check for node names using problematic characters: > find doc -name '*.texi' -exec grep '^@node[^,]*[:.()]' {} + > Sadly makeinfo does not warn about such characters. > > Running that gives me some matches: > > doc/misc/modus-themes.texi:@node Advanced customization (do-it-yourself) > doc/misc/modus-themes.texi:@node Per-theme customization settings (DIY) (etc) I think this has to be fixed in the Modus manual, so I've added Protesilaos to the CCs. (The issue is that parentheses aren't valid in texinfo node names, apparently.) > doc/misc/org.texi:@node Hooks (2) And in the Org manual, so I've added Kyle to the CCs, too. -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no From debbugs-submit-bounces@debbugs.gnu.org Mon Nov 29 12:44:25 2021 Received: (at 52126) by debbugs.gnu.org; 29 Nov 2021 17:44:25 +0000 Received: from localhost ([127.0.0.1]:39239 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mrkhV-0004UN-FR for submit@debbugs.gnu.org; Mon, 29 Nov 2021 12:44:25 -0500 Received: from mail-pf1-f182.google.com ([209.85.210.182]:34651) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mrkhT-0004U7-E1 for 52126@debbugs.gnu.org; Mon, 29 Nov 2021 12:44:23 -0500 Received: by mail-pf1-f182.google.com with SMTP id r130so17719004pfc.1 for <52126@debbugs.gnu.org>; Mon, 29 Nov 2021 09:44:23 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=nsnrXPD7W+g6xro+JTe7igu6e1YtJcHAi+NVh3F0kQo=; b=g3cCcbLxHfjTTl7B1n9d3zLKr76sdVsDroBi92bVTkuf/RjqLra5LkAdaL4NeiZha0 FhZBitIdcBqPDgVHyCOe3iVIa7fDTVWI5bjhhj5JopA6vMDmMC0pk9/X38y/deQlLUG9 rWJPFArdjEveQoH+sxFHWX/tjvCYzqsIpmAl3l+6w0couuD3h1EnlZd1uc063pnUdyF1 nU/KEmxeo5fDwzi7tR6K/kHbb0EwlN/tsuPk7s42EdNbseso6ZftA9PmFCKR9X6S++SV YFFbf5MoRf6+mAxOEDOeT+jl+336BTjksjDut0bl3o96wnZGY2urpLxOOX1aaP+xISI0 X5LQ== X-Gm-Message-State: AOAM532QZ/UFf0DF4u0MIBR7Ed34u03jrzFBuiaI4sAbUOYMwmVkUDSq p25xqXd8tHxpWVoiHPfXsvmZJi0oNwcjt/3qLUc= X-Google-Smtp-Source: ABdhPJwfjfc+HuNq3FObNJkIFqvPBg68IWNakYEjoN4YxSaM8bHv237d0UztHcY83FxZYW7qM8jIgzqiAHeVhC2YuBA= X-Received: by 2002:a63:4f57:: with SMTP id p23mr35860056pgl.325.1638207857630; Mon, 29 Nov 2021 09:44:17 -0800 (PST) Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Mon, 29 Nov 2021 09:44:17 -0800 From: Stefan Kangas In-Reply-To: <871r2zueyw.fsf@gnus.org> References: <871r2zueyw.fsf@gnus.org> MIME-Version: 1.0 Date: Mon, 29 Nov 2021 09:44:17 -0800 Message-ID: Subject: Re: bug#52126: Problematic characters in info node names To: Lars Ingebrigtsen Content-Type: text/plain; charset="UTF-8" X-Spam-Score: 0.5 (/) X-Debbugs-Envelope-To: 52126 Cc: 52126@debbugs.gnu.org, Protesilaos Stavrou , Kyle Meyer , Glenn Morris X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -0.5 (/) Lars Ingebrigtsen writes: >> ** Manuals >> Check for node names using problematic characters: >> find doc -name '*.texi' -exec grep '^@node[^,]*[:.()]' {} + >> Sadly makeinfo does not warn about such characters. Did something change here since the above note in admin/release-process was written in 2013 (commit 16bcc96df4)? I read in (info "(texinfo) Node Line Requirements") that: * Unfortunately, you cannot reliably use periods, commas, or colons within a node name; these can confuse the Info reader. Also, a node name may not start with a left parenthesis preceding a right parenthesis, as in '(not)allowed', since this syntax is used to specify an external manual. (Perhaps these limitations will be removed some day.) 'makeinfo' warns about such problematic usage in node names, menu items, and cross-references. If you don't want to see the warnings, you can set the customization variable 'INFO_SPECIAL_CHARS_WARNING' to '0' (*note Other Customization Variables::). (Though I can't see any warnings produced when running "make info" in a fresh tree.) From debbugs-submit-bounces@debbugs.gnu.org Mon Nov 29 12:52:53 2021 Received: (at 52126) by debbugs.gnu.org; 29 Nov 2021 17:52:53 +0000 Received: from localhost ([127.0.0.1]:39245 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mrkph-0004ix-AR for submit@debbugs.gnu.org; Mon, 29 Nov 2021 12:52:53 -0500 Received: from eggs.gnu.org ([209.51.188.92]:37040) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mrkpf-0004im-TU for 52126@debbugs.gnu.org; Mon, 29 Nov 2021 12:52:52 -0500 Received: from [2001:470:142:3::e] (port=53420 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mrkpZ-0006Vr-5M; Mon, 29 Nov 2021 12:52:45 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=+l3drpRqa4NhdaIBY2CLETdkPv3J1d1Icm02bQ3WNu4=; b=U7yzl4m/0k9E qzLQZ74CBfE0LOdB9M+CwpKexZ9YR8z5wnEAz5Z3OfGdXIYAjDs2QQ7QYB/dfRaisAncC0U96hAgn pV/W7HxgTxhi8PkxMYcadiqncGKeRICcn3vpcc3aqrRbKMN0SYlOd+bE73ldzNCT9zxpuxNbAI3Rd s9/sRephciWc5f6jzMljKZIWoMNLPHfMpT9voP2C0vJS3Jv+lUOpNhgdcvgJbBMlAHJ2mZe/1FRdI 7jZ1vIU/MiUAeo1Ej/l3pSoO7LJf8toFOA+DJ6uu6v7vu0qNZ+2X3U5MNBl1PtQaXgF01loYdEjYM +kZ7Gn7RAo9EYscAm7omjA==; Received: from [87.69.77.57] (port=4756 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mrkpY-0007MZ-Rf; Mon, 29 Nov 2021 12:52:45 -0500 Date: Mon, 29 Nov 2021 19:52:57 +0200 Message-Id: <83ee6yvog6.fsf@gnu.org> From: Eli Zaretskii To: Stefan Kangas In-Reply-To: (message from Stefan Kangas on Mon, 29 Nov 2021 09:44:17 -0800) Subject: Re: bug#52126: Problematic characters in info node names References: <871r2zueyw.fsf@gnus.org> X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 52126 Cc: 52126@debbugs.gnu.org, larsi@gnus.org, info@protesilaos.com, rgm@gnu.org, kyle@kyleam.com X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) > From: Stefan Kangas > Date: Mon, 29 Nov 2021 09:44:17 -0800 > Cc: 52126@debbugs.gnu.org, Protesilaos Stavrou , > Kyle Meyer , Glenn Morris > > I read in (info "(texinfo) Node Line Requirements") that: > > * Unfortunately, you cannot reliably use periods, commas, or colons > within a node name; these can confuse the Info reader. Also, a > node name may not start with a left parenthesis preceding a right > parenthesis, as in '(not)allowed', since this syntax is used to > specify an external manual. (Perhaps these limitations will be > removed some day.) This is mainly because of the stand-alone Info reader. The Emacs Info mode copes with these characters in node names much better. So yes, it is desirable to avoid them, but it isn't a catastrophe if they are there. From debbugs-submit-bounces@debbugs.gnu.org Mon Nov 29 13:04:48 2021 Received: (at 52126) by debbugs.gnu.org; 29 Nov 2021 18:04:48 +0000 Received: from localhost ([127.0.0.1]:39274 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mrl1E-00052k-3n for submit@debbugs.gnu.org; Mon, 29 Nov 2021 13:04:48 -0500 Received: from relay9-d.mail.gandi.net ([217.70.183.199]:59873) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mrl1C-00052V-Rh for 52126@debbugs.gnu.org; Mon, 29 Nov 2021 13:04:47 -0500 Received: (Authenticated sender: public@protesilaos.com) by relay9-d.mail.gandi.net (Postfix) with ESMTPSA id 05536FF802; Mon, 29 Nov 2021 18:04:38 +0000 (UTC) From: Protesilaos Stavrou To: Eli Zaretskii Subject: Re: bug#52126: Problematic characters in info node names In-Reply-To: <83ee6yvog6.fsf@gnu.org> References: <871r2zueyw.fsf@gnus.org> <83ee6yvog6.fsf@gnu.org> User-Agent: Notmuch/0.34.1 (https://notmuchmail.org) Emacs/29.0.50 (x86_64-pc-linux-gnu) Date: Mon, 29 Nov 2021 20:04:37 +0200 Message-ID: <877dcqn8i2.fsf@protesilaos.com> MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: -0.7 (/) X-Debbugs-Envelope-To: 52126 Cc: 52126@debbugs.gnu.org, larsi@gnus.org, Stefan Kangas , kyle@kyleam.com, rgm@gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.7 (-) On 2021-11-29, 19:52 +0200, Eli Zaretskii wrote: >> From: Stefan Kangas >> Date: Mon, 29 Nov 2021 09:44:17 -0800 >> Cc: 52126@debbugs.gnu.org, Protesilaos Stavrou , >> Kyle Meyer , Glenn Morris >> >> I read in (info "(texinfo) Node Line Requirements") that: >> >> * Unfortunately, you cannot reliably use periods, commas, or colons >> within a node name; these can confuse the Info reader. Also, a >> node name may not start with a left parenthesis preceding a right >> parenthesis, as in '(not)allowed', since this syntax is used to >> specify an external manual. (Perhaps these limitations will be >> removed some day.) > > This is mainly because of the stand-alone Info reader. The Emacs Info > mode copes with these characters in node names much better. > > So yes, it is desirable to avoid them, but it isn't a catastrophe if > they are there. Thanks! I just removed the problematic characters from my repo. Though this change will be brought into emacs.git as part of my next tagged release (in a few weeks). Two questions then: 1. Do you want me to change this now on the trunk? 2. This affects the emacs-28 branch. Should I patch that as well? -- Protesilaos Stavrou https://protesilaos.com From debbugs-submit-bounces@debbugs.gnu.org Mon Nov 29 13:07:54 2021 Received: (at 52126) by debbugs.gnu.org; 29 Nov 2021 18:07:54 +0000 Received: from localhost ([127.0.0.1]:39284 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mrl4A-00057X-Qn for submit@debbugs.gnu.org; Mon, 29 Nov 2021 13:07:54 -0500 Received: from eggs.gnu.org ([209.51.188.92]:41944) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mrl48-00057J-RX for 52126@debbugs.gnu.org; Mon, 29 Nov 2021 13:07:49 -0500 Received: from [2001:470:142:3::e] (port=54340 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mrl42-0000LZ-Q3; Mon, 29 Nov 2021 13:07:42 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=bb+VsHXFzf89vTOU6julPn1mxC+FtynJyDoLD8+HwIA=; b=Y70mMvYsz5X/ lNKY/q/3MwyzNNfxcPgmhMT8LDn9edMIMCJxdd0Sia3zjk3bQpZjnJSvHEH+E3Gn6VjIvEuO8nwZA 0bRSyQ+rzrCdEw2OfFe2hdXwoby2YzSb2JgF+f7r0o7KmMNS7t9TYq7K+k8qm18QsOkv9e126qefY cdA5kxqxCUj9J0Vu0Nr35QnxY1oC2B1ZRuXdctjgmH7oDwWI2erQUYLbIZd9MqS9zHE3yLaLDZm1L bwR3uxQ4VtaI3PPBnfKlR7CnR7M74dw5dPbJXybByuYmIyctzr5yIHBrH1DyrwJy9XLRAst/JajYw m+EtvBRgCvbT0jB38Kax5g==; Received: from [87.69.77.57] (port=1705 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mrl42-0003V0-GF; Mon, 29 Nov 2021 13:07:42 -0500 Date: Mon, 29 Nov 2021 20:07:54 +0200 Message-Id: <83czmivnr9.fsf@gnu.org> From: Eli Zaretskii To: Protesilaos Stavrou In-Reply-To: <877dcqn8i2.fsf@protesilaos.com> (message from Protesilaos Stavrou on Mon, 29 Nov 2021 20:04:37 +0200) Subject: Re: bug#52126: Problematic characters in info node names References: <871r2zueyw.fsf@gnus.org> <83ee6yvog6.fsf@gnu.org> <877dcqn8i2.fsf@protesilaos.com> X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 52126 Cc: 52126@debbugs.gnu.org, larsi@gnus.org, stefan@marxist.se, kyle@kyleam.com, rgm@gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) > From: Protesilaos Stavrou > Cc: larsi@gnus.org, Stefan Kangas , > 52126@debbugs.gnu.org, kyle@kyleam.com, rgm@gnu.org > Date: Mon, 29 Nov 2021 20:04:37 +0200 > > 1. Do you want me to change this now on the trunk? Yes. > 2. This affects the emacs-28 branch. Should I patch that as well? It's up to you. It isn't important either way. From debbugs-submit-bounces@debbugs.gnu.org Mon Nov 29 13:17:42 2021 Received: (at 52126) by debbugs.gnu.org; 29 Nov 2021 18:17:42 +0000 Received: from localhost ([127.0.0.1]:39302 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mrlDi-0005MU-Gn for submit@debbugs.gnu.org; Mon, 29 Nov 2021 13:17:42 -0500 Received: from eggs.gnu.org ([209.51.188.92]:44352) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mrlDg-0005MG-Et for 52126@debbugs.gnu.org; Mon, 29 Nov 2021 13:17:41 -0500 Received: from [2001:470:142:3::e] (port=54810 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mrlDa-0001ex-Fb; Mon, 29 Nov 2021 13:17:34 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-Version:In-Reply-To:Date:References:Subject:To: From; bh=QI6D6TodVSC1EPXwXPi7j81c6iga6LXLlYmlr4J0bC4=; b=JU6f40hb67hCJt0pj7hr yax4Kse3NabnZ1Dxy5/FnoMWJkZH3e7kablOSu5ondVVUOG5S9laQRH9Q2vgU/Z1hGVvd1vje1YSS fD3cqhdHOQXzJ0DaQ3kxdj5A2HIwp6QfdEZnULm+OGBFJ6JPr3x9mh3lRFLEEmCI/gT9l0Yy0CRcF fn8NMtGBjhq6W2P2Vkd77CZqvxWjxo9S/0q/VvUMA3xfe7qrMsL3g3EFfXDUKgBWMqiB2LAO4zaeR 2kbGAUDwFe9fHPFJouz1waXB7bVyVDph66j76CnbjR3/c3nsFe4OSX4zhXQgV8VPfIwn4Q4/vWDuG UFVeCOF5UnZaWA==; Received: from rgm by fencepost.gnu.org with local (Exim 4.90_1) (envelope-from ) id 1mrlDY-0004hw-D7; Mon, 29 Nov 2021 13:17:33 -0500 From: Glenn Morris To: Stefan Kangas Subject: Re: bug#52126: Problematic characters in info node names References: <871r2zueyw.fsf@gnus.org> X-Spook: Suicide attack Locks Dolch BBE Indigo cdi FARC SIN X-Ran: @qzMl++KiMINqpN]3X)/'!7\c3|sUR=R_\m9nMs.dh}$G%m#)X^hDGM6~w:W%#w!.aw_VW X-Hue: cyan X-Debbugs-No-Ack: yes X-Attribution: GM Date: Mon, 29 Nov 2021 13:17:32 -0500 In-Reply-To: (Stefan Kangas's message of "Mon, 29 Nov 2021 09:44:17 -0800") Message-ID: <60pmqihlmr.fsf@fencepost.gnu.org> User-Agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 52126 Cc: 52126@debbugs.gnu.org, Lars Ingebrigtsen , Protesilaos Stavrou , Kyle Meyer X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) Stefan Kangas wrote: > Did something change here since the above note in admin/release-process > was written in 2013 (commit 16bcc96df4)? Yes. It's easy to find old versions of the Texinfo manual, eg http://www.nongnu.org/texi2latex/texinfo/Node-Line-Requirements.html Newer Texinfo is less strict, but Emacs configure still claims to support 4.13. > (Though I can't see any warnings produced when running "make info" in a > fresh tree.) It never did warn about such things; it made no sense to me. https://lists.gnu.org/r/bug-texinfo/2013-08/msg00008.html From debbugs-submit-bounces@debbugs.gnu.org Mon Nov 29 13:31:59 2021 Received: (at 52126) by debbugs.gnu.org; 29 Nov 2021 18:31:59 +0000 Received: from localhost ([127.0.0.1]:39346 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mrlRX-0007Pf-BE for submit@debbugs.gnu.org; Mon, 29 Nov 2021 13:31:59 -0500 Received: from mail-pj1-f44.google.com ([209.85.216.44]:52131) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mrlRU-0007JZ-NA for 52126@debbugs.gnu.org; Mon, 29 Nov 2021 13:31:57 -0500 Received: by mail-pj1-f44.google.com with SMTP id gt5so13373314pjb.1 for <52126@debbugs.gnu.org>; Mon, 29 Nov 2021 10:31:56 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=YR27D5uYZhL4JcDjrcmAgF/gspRc6x4gzFfeTwfGASw=; b=L+ygNCZwoqd3yRIpZuMlyjZixvXL3oxdDh/IrUUCWM8fsyxFsz094cn3e3PFCOgmg/ uHWtYt/gsCOgVyrNHxced19wDhAwyLLC2xhGyC9n/s5ehuzBnmu9thBEMfZ7b4u+JWCe 9n0mhr8JmzqSEON3coIfNGK96aY3L2RzEUksiYVdIVvz8fq67VzOrc6RSyVyBv8hIiSM znqhFHn9Cu4ajQgAKJWS0vPYKqDjyRf7MNwptsul7afJGY2E3/38XxZeg3bY84+nWcKw va4bxGeI12xMkpFKzDYecZMgajBneB6oBmLW1OaKo03MeMhM8HtJW2pReW8Jf6xWDloC O/yw== X-Gm-Message-State: AOAM5339fYujQ8ZUFIhnw2L0Pp0ilWVU4qjBYpakdtSdElt1LLddJJXK qi5rz2qXlatqr4GH0ig21AIIZZvw5TC6zznIqUI= X-Google-Smtp-Source: ABdhPJz7hurbek2YaQmWSlTqA/WNRoz5WKcWIzaNCJY+JrE5TRfQIiLK3PzDB/W0cK6Mv6Bk8k6F/jDal0vr+PrnBK4= X-Received: by 2002:a17:90a:be10:: with SMTP id a16mr38411pjs.133.1638210710869; Mon, 29 Nov 2021 10:31:50 -0800 (PST) Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Mon, 29 Nov 2021 10:31:50 -0800 From: Stefan Kangas In-Reply-To: <83ee6yvog6.fsf@gnu.org> References: <871r2zueyw.fsf@gnus.org> <83ee6yvog6.fsf@gnu.org> MIME-Version: 1.0 Date: Mon, 29 Nov 2021 10:31:50 -0800 Message-ID: Subject: Re: bug#52126: Problematic characters in info node names To: Eli Zaretskii Content-Type: text/plain; charset="UTF-8" X-Spam-Score: 0.5 (/) X-Debbugs-Envelope-To: 52126 Cc: 52126@debbugs.gnu.org, larsi@gnus.org, info@protesilaos.com, rgm@gnu.org, kyle@kyleam.com X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -0.5 (/) Eli Zaretskii writes: >> I read in (info "(texinfo) Node Line Requirements") that: >> >> * Unfortunately, you cannot reliably use periods, commas, or colons >> within a node name; these can confuse the Info reader. Also, a >> node name may not start with a left parenthesis preceding a right >> parenthesis, as in '(not)allowed', since this syntax is used to >> specify an external manual. (Perhaps these limitations will be >> removed some day.) > > This is mainly because of the stand-alone Info reader. The Emacs Info > mode copes with these characters in node names much better. > > So yes, it is desirable to avoid them, but it isn't a catastrophe if > they are there. I guess what I'm asking myself if its useful to keep this advice in admin/release-process. Personally, I have no strong opinion either way, but I note that makeinfo seems to now claim to warn about any problematic cases. From debbugs-submit-bounces@debbugs.gnu.org Mon Nov 29 14:33:01 2021 Received: (at 52126) by debbugs.gnu.org; 29 Nov 2021 19:33:01 +0000 Received: from localhost ([127.0.0.1]:39489 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mrmOW-0003Lu-RY for submit@debbugs.gnu.org; Mon, 29 Nov 2021 14:33:01 -0500 Received: from relay9-d.mail.gandi.net ([217.70.183.199]:51895) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mrmOT-0003GP-K8 for 52126@debbugs.gnu.org; Mon, 29 Nov 2021 14:32:55 -0500 Received: (Authenticated sender: public@protesilaos.com) by relay9-d.mail.gandi.net (Postfix) with ESMTPSA id 91FC2FF802; Mon, 29 Nov 2021 19:32:45 +0000 (UTC) From: Protesilaos Stavrou To: Eli Zaretskii Subject: Re: bug#52126: Problematic characters in info node names In-Reply-To: <83czmivnr9.fsf@gnu.org> References: <871r2zueyw.fsf@gnus.org> <83ee6yvog6.fsf@gnu.org> <877dcqn8i2.fsf@protesilaos.com> <83czmivnr9.fsf@gnu.org> User-Agent: Notmuch/0.34.1 (https://notmuchmail.org) Emacs/29.0.50 (x86_64-pc-linux-gnu) Date: Mon, 29 Nov 2021 21:32:44 +0200 Message-ID: <871r2yn4f7.fsf@protesilaos.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" X-Spam-Score: -0.7 (/) X-Debbugs-Envelope-To: 52126 Cc: 52126@debbugs.gnu.org, larsi@gnus.org, stefan@marxist.se, kyle@kyleam.com, rgm@gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) --=-=-= Content-Type: text/plain On 2021-11-29, 20:07 +0200, Eli Zaretskii wrote: >> From: Protesilaos Stavrou >> Cc: larsi@gnus.org, Stefan Kangas , >> 52126@debbugs.gnu.org, kyle@kyleam.com, rgm@gnu.org >> Date: Mon, 29 Nov 2021 20:04:37 +0200 >> >> 1. Do you want me to change this now on the trunk? > > Yes. > >> 2. This affects the emacs-28 branch. Should I patch that as well? > > It's up to you. It isn't important either way. Both patches are attached. Each file name contains the Emacs version it belongs to. I can push directly from here if you think everything is in order. -- Protesilaos Stavrou https://protesilaos.com --=-=-= Content-Type: text/x-patch Content-Disposition: attachment; filename=0001-Remove-problematic-characters-from-modus-themes-emacs28.patch >From ecf3bf66ba8c9f2805196ece2607d7f1c9cae3d5 Mon Sep 17 00:00:00 2001 Message-Id: From: Protesilaos Stavrou Date: Mon, 29 Nov 2021 21:13:55 +0200 Subject: [PATCH] Remove problematic characters from modus-themes.org (bug#52126) * doc/misc/modus-themes.org (Enable and load, Font configurations for Org and others) (Note on highlight-parentheses.el, Note on god-mode.el): Update links to headings so that they no longer include the removed portions of text. (Option for color-coding success state, Option for line highlighting) (Option for line numbers, Option for parenthesis matching) (Advanced customization, Per-theme customization settings) (Case-by-case face specs using the themes' palette) (Face specs at scale using the themes' palette) (Remap face with local value, Cycle through arbitrary colors) (Override colors, Override color saturation) (Font configurations for Org and others, Configure bold and italic faces) (Custom Org user faces, Update Org block delimiter fontification) (Measure color contrast, Load theme depending on time of day) (Backdrop for pdf-tools) (A theme-agnostic hook for theme loading, Note on EWW and Elfeed fonts) (Frequently Asked Questions): Remove parentheses from headings as they can cause problems in the .texi version of the file. --- doc/misc/modus-themes.org | 66 +++++++++++++++++++-------------------- 1 file changed, 33 insertions(+), 33 deletions(-) diff --git a/doc/misc/modus-themes.org b/doc/misc/modus-themes.org index 675144d517..9674a12e69 100644 --- a/doc/misc/modus-themes.org +++ b/doc/misc/modus-themes.org @@ -279,9 +279,9 @@ * Enable and load 2. The functions will run the ~modus-themes-after-load-theme-hook~ as their final step. This can be employed for bespoke configurations - ([[#h:f4651d55-8c07-46aa-b52b-bed1e53463bb][Advanced customization (do-it-yourself)]]). Experienced users may not - wish to rely on such a hook and the functions that run it: they may - prefer a custom solution ([[#h:86f6906b-f090-46cc-9816-1fe8aeb38776][A theme-agnostic hook for theme loading]]). + ([[#h:f4651d55-8c07-46aa-b52b-bed1e53463bb][Advanced customization]]). Experienced users may not wish to rely + on such a hook and the functions that run it: they may prefer a + custom solution ([[#h:86f6906b-f090-46cc-9816-1fe8aeb38776][A theme-agnostic hook for theme loading]]). ** Sample configuration for use-package :properties: @@ -483,7 +483,7 @@ ** Option for inhibiting theme reload Enable this behaviour by setting this variable to ~nil~. -** Option for color-coding success state (deuteranopia) +** Option for color-coding success state :properties: :alt_title: Success' color-code :description: Toggle blue color for success or done states @@ -1056,7 +1056,7 @@ ** Option for language checkers style, is controlled by the built-in variables ~underline-minimum-offset~, ~x-underline-at-descent-line~, ~x-use-underline-position-properties~. -** Option for line highlighting (hl-line-mode) +** Option for line highlighting :properties: :alt_title: Line highlighting :description: Choose style of current line (hl-line-mode) @@ -1108,7 +1108,7 @@ ** Option for line highlighting (hl-line-mode) This style affects several packages that enable ~hl-line-mode~, such as =elfeed=, =notmuch=, and =mu4e=. -** Option for line numbers (display-line-numbers-mode) +** Option for line numbers :properties: :alt_title: Line numbers :description: Toggle subtle style for line numbers @@ -1137,7 +1137,7 @@ ** Option for line numbers (display-line-numbers-mode) the rest of the buffer. Foreground values for all relevant faces are updated to accommodate this aesthetic. -** Option for parenthesis matching (show-paren-mode) +** Option for parenthesis matching :properties: :alt_title: Matching parentheses :description: Choose between various styles for matching delimiters/parentheses @@ -1723,7 +1723,7 @@ ** Option for variable-pitch font in headings [[#h:defcf4fc-8fa8-4c29-b12e-7119582cc929][Font configurations for Org and others]]. -* Advanced customization (do-it-yourself) +* Advanced customization :properties: :custom_id: h:f4651d55-8c07-46aa-b52b-bed1e53463bb :end: @@ -1738,7 +1738,7 @@ * Advanced customization (do-it-yourself) incompatibilities between versioned releases of the themes. As such, they are labelled as "do-it-yourself" or "DIY". -** Per-theme customization settings (DIY) +** Per-theme customization settings :properties: :custom_id: h:a897b302-8e10-4a26-beab-3caaee1e1193 :end: @@ -1773,7 +1773,7 @@ ** Per-theme customization settings (DIY) For a more elaborate design, it is better to inspect the source code of ~modus-themes-toggle~ and relevant functions. -** Case-by-case face specs using the themes' palette (DIY) +** Case-by-case face specs using the themes' palette :properties: :custom_id: h:1487c631-f4fe-490d-8d58-d72ffa3bd474 :end: @@ -1877,7 +1877,7 @@ ** Case-by-case face specs using the themes' palette (DIY) (set-face-attribute 'cursor nil :background (modus-themes-color-alts 'blue 'red)) #+end_src -** Face specs at scale using the themes' palette (DIY) +** Face specs at scale using the themes' palette :properties: :custom_id: h:51ba3547-b8c8-40d6-ba5a-4586477fd4ae :end: @@ -1992,7 +1992,7 @@ ** Face specs at scale using the themes' palette (DIY) ...)) #+end_src -** Remap face with local value (DIY) +** Remap face with local value :properties: :custom_id: h:7a93cb6f-4eca-4d56-a85c-9dcd813d6b0f :end: @@ -2054,7 +2054,7 @@ ** Remap face with local value (DIY) functions that also accept an arbitrary face. We shall leave the experimentation up to you. -** Cycle through arbitrary colors (DIY) +** Cycle through arbitrary colors :properties: :custom_id: h:77dc4a30-b96a-4849-85a8-fee3c2995305 :end: @@ -2218,7 +2218,7 @@ ** Cycle through arbitrary colors (DIY) ...) #+end_src -** Override colors (DIY) +** Override colors :properties: :custom_id: h:307d95dd-8dbd-4ece-a543-10ae86f155a6 :end: @@ -2334,7 +2334,7 @@ ** Override colors (DIY) ratio between two color values, so it can help in overriding the palette (or a subset thereof) without making the end result inaccessible. -** Override color saturation (DIY) +** Override color saturation :properties: :custom_id: h:4589acdc-2505-41fc-9f5e-699cfc45ab00 :end: @@ -2454,7 +2454,7 @@ ** Override color saturation (DIY) ('modus-vivendi (modus-themes-load-vivendi)))) #+end_src -** Font configurations for Org and others (DIY) +** Font configurations for Org and others :properties: :custom_id: h:defcf4fc-8fa8-4c29-b12e-7119582cc929 :end: @@ -2511,9 +2511,9 @@ ** Font configurations for Org and others (DIY) something like the ~text-scale-adjust~ command which only operates on the base font size (i.e. the ~default~ face's absolute height). -[[#h:e6c5451f-6763-4be7-8fdb-b4706a422a4c][Note for EWW and Elfeed fonts (SHR fonts)]]. +[[#h:e6c5451f-6763-4be7-8fdb-b4706a422a4c][Note for EWW and Elfeed fonts]]. -** Configure bold and italic faces (DIY) +** Configure bold and italic faces :properties: :custom_id: h:2793a224-2109-4f61-a106-721c57c01375 :end: @@ -2605,7 +2605,7 @@ ** Configure bold and italic faces (DIY) (add-hook 'modus-themes-after-load-theme-hook #'my-modes-themes-bold-italic-faces) #+end_src -** Custom Org user faces (DIY) +** Custom Org user faces :properties: :custom_id: h:89f0678d-c5c3-4a57-a526-668b2bb2d7ad :end: @@ -2693,7 +2693,7 @@ ** Custom Org user faces (DIY) [[#h:02e25930-e71a-493d-828a-8907fc80f874][Check color combinations]]. -** Update Org block delimiter fontification (DIY) +** Update Org block delimiter fontification :properties: :custom_id: h:f44cc6e3-b0f1-4a5e-8a90-9e48fa557b50 :end: @@ -2735,7 +2735,7 @@ ** Update Org block delimiter fontification (DIY) (font-lock-flush))) #+end_src -** Measure color contrast (DIY) +** Measure color contrast :properties: :custom_id: h:02e25930-e71a-493d-828a-8907fc80f874 :end: @@ -2808,7 +2808,7 @@ ** Measure color contrast (DIY) Such knowledge may prove valuable while attempting to override some of the themes' colors: [[#h:307d95dd-8dbd-4ece-a543-10ae86f155a6][Override colors]]. -** Load theme depending on time of day (DIY) +** Load theme depending on time of day :properties: :custom_id: h:1d1ef4b4-8600-4a09-993c-6de3af0ddd26 :end: @@ -2835,7 +2835,7 @@ ** Load theme depending on time of day (DIY) (circadian-setup)) #+end_src -** Backdrop for pdf-tools (DIY) +** Backdrop for pdf-tools :properties: :custom_id: h:ff69dfe1-29c0-447a-915c-b5ff7c5509cd :end: @@ -2897,7 +2897,7 @@ ** Backdrop for pdf-tools (DIY) they automatically switch to their dark mode when ~modus-themes-toggle~ is called from inside a buffer whose major-mode is ~pdf-view-mode~. -** A theme-agnostic hook for theme loading (DIY) +** A theme-agnostic hook for theme loading :properties: :custom_id: h:86f6906b-f090-46cc-9816-1fe8aeb38776 :end: @@ -3509,7 +3509,7 @@ ** Note on highlight-parentheses.el "Do-It-Yourself" (DIY) sections, which provide insight into the more advanced customization options of the themes. -[[#h:f4651d55-8c07-46aa-b52b-bed1e53463bb][Advanced customization (do-it-yourself)]]. +[[#h:f4651d55-8c07-46aa-b52b-bed1e53463bb][Advanced customization]]. In the following example, we are assuming that the user wants to (i) re-use color variables provided by the themes, (ii) be able to retain @@ -3775,12 +3775,12 @@ ** Note on god-mode.el :custom_id: h:4da1d515-3e05-47ef-9e45-8251fc7e986a :end: -The ~god-mode~ library does not provide faces that could be configured by -the Modus themes. Users who would like to get some visual feedback on -the status of {{{kbd(M-x god-mode)}}} are instead encouraged by upstream to -set up their own configurations, such as by changing the ~mode-line~ face -([[#h:f4651d55-8c07-46aa-b52b-bed1e53463bb][Advanced customization (do-it-yourself)]]). This is an adaptation of the -approach followed in the upstream README: +The ~god-mode~ library does not provide faces that could be configured +by the Modus themes. Users who would like to get some visual feedback +on the status of {{{kbd(M-x god-mode)}}} are instead encouraged by upstream +to set up their own configurations, such as by changing the ~mode-line~ +face ([[#h:f4651d55-8c07-46aa-b52b-bed1e53463bb][Advanced customization]]). This is an adaptation of the approach +followed in the upstream README: #+begin_src emacs-lisp (defun my-god-mode-update-mode-line () @@ -3874,7 +3874,7 @@ ** Note on SHR colors Consult {{{kbd(C-h v shr-use-colors)}}}. -** Note on EWW and Elfeed fonts (SHR fonts) +** Note on EWW and Elfeed fonts :properties: :custom_id: h:e6c5451f-6763-4be7-8fdb-b4706a422a4c :end: @@ -3988,7 +3988,7 @@ ** Note on pdf-tools link hints "-draw" "text %X,%Y '%c'")))) #+end_src -* Frequently Asked Questions (FAQ) +* Frequently Asked Questions :properties: :custom_id: h:b3384767-30d3-4484-ba7f-081729f03a47 :end: -- 2.34.0 --=-=-= Content-Type: text/x-patch Content-Disposition: attachment; filename=0001-Remove-problematic-characters-from-modus-themes-emacs29.patch >From 030a5c570487e2809a1ae902f43d1fecf381030c Mon Sep 17 00:00:00 2001 Message-Id: <030a5c570487e2809a1ae902f43d1fecf381030c.1638213514.git.info@protesilaos.com> From: Protesilaos Stavrou Date: Mon, 29 Nov 2021 21:06:52 +0200 Subject: [PATCH] Remove problematic characters from modus-themes.org (bug#52126) * doc/misc/modus-themes.org (Enable and load, Font configurations for Org and others) (Note on highlight-parentheses.el, Note on god-mode.el): Update links to headings so that they no longer include the removed portions of text. (Option for color-coding success state, Option for line highlighting) (Option for line numbers, Option for parenthesis matching) (Advanced customization, Per-theme customization settings) (Case-by-case face specs using the themes' palette) (Face specs at scale using the themes' palette) (Remap face with local value, Cycle through arbitrary colors) (Override colors, Override color saturation) (Font configurations for Org and others, Configure bold and italic faces) (Custom Org user faces, Update Org block delimiter fontification) (Measure color contrast, Load theme depending on time of day) (Backdrop for pdf-tools, Decrease mode line height) (A theme-agnostic hook for theme loading, Note on EWW and Elfeed fonts) (Frequently Asked Questions): Remove parentheses from headings as they can cause problems in the .texi version of the file. --- doc/misc/modus-themes.org | 68 +++++++++++++++++++-------------------- 1 file changed, 34 insertions(+), 34 deletions(-) diff --git a/doc/misc/modus-themes.org b/doc/misc/modus-themes.org index f3c2e37b7d..f67a179567 100644 --- a/doc/misc/modus-themes.org +++ b/doc/misc/modus-themes.org @@ -279,9 +279,9 @@ * Enable and load 2. The functions will run the ~modus-themes-after-load-theme-hook~ as their final step. This can be employed for bespoke configurations - ([[#h:f4651d55-8c07-46aa-b52b-bed1e53463bb][Advanced customization (do-it-yourself)]]). Experienced users may not - wish to rely on such a hook and the functions that run it: they may - prefer a custom solution ([[#h:86f6906b-f090-46cc-9816-1fe8aeb38776][A theme-agnostic hook for theme loading]]). + ([[#h:f4651d55-8c07-46aa-b52b-bed1e53463bb][Advanced customization]]). Experienced users may not wish to rely + on such a hook and the functions that run it: they may prefer a + custom solution ([[#h:86f6906b-f090-46cc-9816-1fe8aeb38776][A theme-agnostic hook for theme loading]]). ** Sample configuration with and without use-package :properties: @@ -515,7 +515,7 @@ ** Option for inhibiting theme reload Regardless of this option, the active theme must be reloaded for changes to user options to take effect ([[#h:3f3c3728-1b34-437d-9d0c-b110f5b161a9][Enable and load]]). -** Option for color-coding success state (deuteranopia) +** Option for color-coding success state :properties: :alt_title: Success' color-code :description: Toggle blue color for success or done states @@ -1151,7 +1151,7 @@ ** Option for language checkers ~flymake-fringe-indicator-position~ and ~flycheck-indication-mode~, respectively. -** Option for line highlighting (hl-line-mode) +** Option for line highlighting :properties: :alt_title: Line highlighting :description: Choose style of current line (hl-line-mode) @@ -1205,7 +1205,7 @@ ** Option for line highlighting (hl-line-mode) This style affects several packages that enable ~hl-line-mode~, such as =elfeed=, =notmuch=, and =mu4e=. -** Option for line numbers (display-line-numbers-mode) +** Option for line numbers :properties: :alt_title: Line numbers :description: Toggle subtle style for line numbers @@ -1260,7 +1260,7 @@ ** Option for intense markup in Org and others With a non-nil value (~t~), these constructs will use a more prominent background and foreground color combination instead. -** Option for parenthesis matching (show-paren-mode) +** Option for parenthesis matching :properties: :alt_title: Matching parentheses :description: Choose between various styles for matching delimiters/parentheses @@ -1913,7 +1913,7 @@ ** Option for variable-pitch font in headings [[#h:defcf4fc-8fa8-4c29-b12e-7119582cc929][Font configurations for Org and others]]. -* Advanced customization (do-it-yourself) +* Advanced customization :properties: :custom_id: h:f4651d55-8c07-46aa-b52b-bed1e53463bb :end: @@ -1928,7 +1928,7 @@ * Advanced customization (do-it-yourself) incompatibilities between versioned releases of the themes. As such, they are labelled as "do-it-yourself" or "DIY". -** Per-theme customization settings (DIY) +** Per-theme customization settings :properties: :custom_id: h:a897b302-8e10-4a26-beab-3caaee1e1193 :end: @@ -1963,7 +1963,7 @@ ** Per-theme customization settings (DIY) For a more elaborate design, it is better to inspect the source code of ~modus-themes-toggle~ and relevant functions. -** Case-by-case face specs using the themes' palette (DIY) +** Case-by-case face specs using the themes' palette :properties: :custom_id: h:1487c631-f4fe-490d-8d58-d72ffa3bd474 :end: @@ -2067,7 +2067,7 @@ ** Case-by-case face specs using the themes' palette (DIY) (set-face-attribute 'cursor nil :background (modus-themes-color-alts 'blue 'red)) #+end_src -** Face specs at scale using the themes' palette (DIY) +** Face specs at scale using the themes' palette :properties: :custom_id: h:51ba3547-b8c8-40d6-ba5a-4586477fd4ae :end: @@ -2182,7 +2182,7 @@ ** Face specs at scale using the themes' palette (DIY) ...)) #+end_src -** Remap face with local value (DIY) +** Remap face with local value :properties: :custom_id: h:7a93cb6f-4eca-4d56-a85c-9dcd813d6b0f :end: @@ -2244,7 +2244,7 @@ ** Remap face with local value (DIY) functions that also accept an arbitrary face. We shall leave the experimentation up to you. -** Cycle through arbitrary colors (DIY) +** Cycle through arbitrary colors :properties: :custom_id: h:77dc4a30-b96a-4849-85a8-fee3c2995305 :end: @@ -2408,7 +2408,7 @@ ** Cycle through arbitrary colors (DIY) ...) #+end_src -** Override colors (DIY) +** Override colors :properties: :custom_id: h:307d95dd-8dbd-4ece-a543-10ae86f155a6 :end: @@ -2524,7 +2524,7 @@ ** Override colors (DIY) ratio between two color values, so it can help in overriding the palette (or a subset thereof) without making the end result inaccessible. -** Override color saturation (DIY) +** Override color saturation :properties: :custom_id: h:4589acdc-2505-41fc-9f5e-699cfc45ab00 :end: @@ -2644,7 +2644,7 @@ ** Override color saturation (DIY) ('modus-vivendi (modus-themes-load-vivendi)))) #+end_src -** Font configurations for Org and others (DIY) +** Font configurations for Org and others :properties: :custom_id: h:defcf4fc-8fa8-4c29-b12e-7119582cc929 :end: @@ -2708,9 +2708,9 @@ ** Font configurations for Org and others (DIY) which only operates on the base font size (i.e. the ~default~ face's absolute height). -[[#h:e6c5451f-6763-4be7-8fdb-b4706a422a4c][Note for EWW and Elfeed fonts (SHR fonts)]]. +[[#h:e6c5451f-6763-4be7-8fdb-b4706a422a4c][Note for EWW and Elfeed fonts]]. -** Configure bold and italic faces (DIY) +** Configure bold and italic faces :properties: :custom_id: h:2793a224-2109-4f61-a106-721c57c01375 :end: @@ -2805,7 +2805,7 @@ ** Configure bold and italic faces (DIY) [[#h:51ba3547-b8c8-40d6-ba5a-4586477fd4ae][Face specs at scale using the themes' palette]]. -** Custom Org user faces (DIY) +** Custom Org user faces :properties: :custom_id: h:89f0678d-c5c3-4a57-a526-668b2bb2d7ad :end: @@ -2893,7 +2893,7 @@ ** Custom Org user faces (DIY) [[#h:02e25930-e71a-493d-828a-8907fc80f874][Check color combinations]]. -** Update Org block delimiter fontification (DIY) +** Update Org block delimiter fontification :properties: :custom_id: h:f44cc6e3-b0f1-4a5e-8a90-9e48fa557b50 :end: @@ -2935,7 +2935,7 @@ ** Update Org block delimiter fontification (DIY) (font-lock-flush))) #+end_src -** Measure color contrast (DIY) +** Measure color contrast :properties: :custom_id: h:02e25930-e71a-493d-828a-8907fc80f874 :end: @@ -3008,7 +3008,7 @@ ** Measure color contrast (DIY) Such knowledge may prove valuable while attempting to override some of the themes' colors: [[#h:307d95dd-8dbd-4ece-a543-10ae86f155a6][Override colors]]. -** Load theme depending on time of day (DIY) +** Load theme depending on time of day :properties: :custom_id: h:1d1ef4b4-8600-4a09-993c-6de3af0ddd26 :end: @@ -3035,7 +3035,7 @@ ** Load theme depending on time of day (DIY) (circadian-setup)) #+end_src -** Backdrop for pdf-tools (DIY) +** Backdrop for pdf-tools :properties: :custom_id: h:ff69dfe1-29c0-447a-915c-b5ff7c5509cd :end: @@ -3097,7 +3097,7 @@ ** Backdrop for pdf-tools (DIY) they automatically switch to their dark mode when ~modus-themes-toggle~ is called from inside a buffer whose major-mode is ~pdf-view-mode~. -** Decrease mode line height (DIY) +** Decrease mode line height :properties: :custom_id: h:03be4438-dae1-4961-9596-60a307c070b5 :end: @@ -3192,7 +3192,7 @@ ** Decrease mode line height (DIY) (add-hook 'modus-themes-after-load-theme-hook #'my-modus-themes-custom-faces) #+end_src -** A theme-agnostic hook for theme loading (DIY) +** A theme-agnostic hook for theme loading :properties: :custom_id: h:86f6906b-f090-46cc-9816-1fe8aeb38776 :end: @@ -3806,7 +3806,7 @@ ** Note on highlight-parentheses.el "Do-It-Yourself" (DIY) sections, which provide insight into the more advanced customization options of the themes. -[[#h:f4651d55-8c07-46aa-b52b-bed1e53463bb][Advanced customization (do-it-yourself)]]. +[[#h:f4651d55-8c07-46aa-b52b-bed1e53463bb][Advanced customization]]. In the following example, we are assuming that the user wants to (i) re-use color variables provided by the themes, (ii) be able to retain @@ -4072,12 +4072,12 @@ ** Note on god-mode.el :custom_id: h:4da1d515-3e05-47ef-9e45-8251fc7e986a :end: -The ~god-mode~ library does not provide faces that could be configured by -the Modus themes. Users who would like to get some visual feedback on -the status of {{{kbd(M-x god-mode)}}} are instead encouraged by upstream to -set up their own configurations, such as by changing the ~mode-line~ face -([[#h:f4651d55-8c07-46aa-b52b-bed1e53463bb][Advanced customization (do-it-yourself)]]). This is an adaptation of the -approach followed in the upstream README: +The ~god-mode~ library does not provide faces that could be configured +by the Modus themes. Users who would like to get some visual feedback +on the status of {{{kbd(M-x god-mode)}}} are instead encouraged by upstream +to set up their own configurations, such as by changing the ~mode-line~ +face ([[#h:f4651d55-8c07-46aa-b52b-bed1e53463bb][Advanced customization]]). This is an adaptation of the approach +followed in the upstream README: #+begin_src emacs-lisp (defun my-god-mode-update-mode-line () @@ -4171,7 +4171,7 @@ ** Note on SHR colors Consult {{{kbd(C-h v shr-use-colors)}}}. -** Note on EWW and Elfeed fonts (SHR fonts) +** Note on EWW and Elfeed fonts :properties: :custom_id: h:e6c5451f-6763-4be7-8fdb-b4706a422a4c :end: @@ -4285,7 +4285,7 @@ ** Note on pdf-tools link hints "-draw" "text %X,%Y '%c'")))) #+end_src -* Frequently Asked Questions (FAQ) +* Frequently Asked Questions :properties: :custom_id: h:b3384767-30d3-4484-ba7f-081729f03a47 :end: -- 2.34.0 --=-=-=-- From debbugs-submit-bounces@debbugs.gnu.org Mon Nov 29 14:46:11 2021 Received: (at 52126) by debbugs.gnu.org; 29 Nov 2021 19:46:11 +0000 Received: from localhost ([127.0.0.1]:39524 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mrmbH-0004et-RU for submit@debbugs.gnu.org; Mon, 29 Nov 2021 14:46:11 -0500 Received: from eggs.gnu.org ([209.51.188.92]:40218) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mrmbC-0004WO-Rl for 52126@debbugs.gnu.org; Mon, 29 Nov 2021 14:46:06 -0500 Received: from [2001:470:142:3::e] (port=57670 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mrmb6-0005tF-Ar; Mon, 29 Nov 2021 14:45:56 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=6TLR+pyuxtMnX49PmL6L7cr/IG5C/s4nhhpEH68dA2o=; b=eNQvYG7QjAWH 6M9pyBDQT3CEaIJUlVCbC5cMSMBYbEFblLhOwH8t3AYU61m9pTCVZX1i5egDtrCl0AOGPJXehxn/v Ri83sUQoREaoEqaijzkcXln9F7cBsnaRmBvN7xpayPQlp03oLmTUezh2ngiALqz1o6ZHrhWY30/Z5 wo0bOp9ZAXRh5Bljb9iVrG9wXzbBgMiuRTpUPymwQM02EgUMS45uhjIlbb/J4sWS2c/im3/bd9f4s 6SgOE5IC+xkvzp9Q3efTV0Feum0QqK4g4+F9DkqluBmJZzpX3N+OzDHjj1dCUO6YwhPV94BStsjAp lYr2eTZ78qLGZ0R7VMUPIw==; Received: from [87.69.77.57] (port=3978 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mrmb6-0005lv-01; Mon, 29 Nov 2021 14:45:56 -0500 Date: Mon, 29 Nov 2021 21:46:08 +0200 Message-Id: <83a6hmvj7j.fsf@gnu.org> From: Eli Zaretskii To: Protesilaos Stavrou In-Reply-To: <871r2yn4f7.fsf@protesilaos.com> (message from Protesilaos Stavrou on Mon, 29 Nov 2021 21:32:44 +0200) Subject: Re: bug#52126: Problematic characters in info node names References: <871r2zueyw.fsf@gnus.org> <83ee6yvog6.fsf@gnu.org> <877dcqn8i2.fsf@protesilaos.com> <83czmivnr9.fsf@gnu.org> <871r2yn4f7.fsf@protesilaos.com> X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 52126 Cc: 52126@debbugs.gnu.org, larsi@gnus.org, stefan@marxist.se, kyle@kyleam.com, rgm@gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) > From: Protesilaos Stavrou > Cc: larsi@gnus.org, stefan@marxist.se, 52126@debbugs.gnu.org, > kyle@kyleam.com, rgm@gnu.org > Date: Mon, 29 Nov 2021 21:32:44 +0200 > > >> 2. This affects the emacs-28 branch. Should I patch that as well? > > > > It's up to you. It isn't important either way. > > Both patches are attached. Each file name contains the Emacs version it > belongs to. > > I can push directly from here if you think everything is in order. Feel free to push to any of the two branches. Thanks. From debbugs-submit-bounces@debbugs.gnu.org Mon Nov 29 15:08:11 2021 Received: (at 52126) by debbugs.gnu.org; 29 Nov 2021 20:08:11 +0000 Received: from localhost ([127.0.0.1]:39541 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mrmwd-0006WC-0L for submit@debbugs.gnu.org; Mon, 29 Nov 2021 15:08:11 -0500 Received: from relay4-d.mail.gandi.net ([217.70.183.196]:45679) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mrmwa-0006Vw-Co for 52126@debbugs.gnu.org; Mon, 29 Nov 2021 15:08:09 -0500 Received: (Authenticated sender: public@protesilaos.com) by relay4-d.mail.gandi.net (Postfix) with ESMTPSA id 24A91E000A; Mon, 29 Nov 2021 20:07:59 +0000 (UTC) From: Protesilaos Stavrou To: Eli Zaretskii Subject: Re: bug#52126: Problematic characters in info node names In-Reply-To: <83a6hmvj7j.fsf@gnu.org> References: <871r2zueyw.fsf@gnus.org> <83ee6yvog6.fsf@gnu.org> <877dcqn8i2.fsf@protesilaos.com> <83czmivnr9.fsf@gnu.org> <871r2yn4f7.fsf@protesilaos.com> <83a6hmvj7j.fsf@gnu.org> User-Agent: Notmuch/0.34.1 (https://notmuchmail.org) Emacs/29.0.50 (x86_64-pc-linux-gnu) Date: Mon, 29 Nov 2021 22:07:58 +0200 Message-ID: <87y256lo81.fsf@protesilaos.com> MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: -0.7 (/) X-Debbugs-Envelope-To: 52126 Cc: 52126@debbugs.gnu.org, larsi@gnus.org, stefan@marxist.se, kyle@kyleam.com, rgm@gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.7 (-) On 2021-11-29, 21:46 +0200, Eli Zaretskii wrote: >> From: Protesilaos Stavrou >> Cc: larsi@gnus.org, stefan@marxist.se, 52126@debbugs.gnu.org, >> kyle@kyleam.com, rgm@gnu.org >> Date: Mon, 29 Nov 2021 21:32:44 +0200 >> >> >> 2. This affects the emacs-28 branch. Should I patch that as well? >> > >> > It's up to you. It isn't important either way. >> >> Both patches are attached. Each file name contains the Emacs version it >> belongs to. >> >> I can push directly from here if you think everything is in order. > > Feel free to push to any of the two branches. > > Thanks. Done for both. Thank you! -- Protesilaos Stavrou https://protesilaos.com From debbugs-submit-bounces@debbugs.gnu.org Mon Nov 29 15:32:58 2021 Received: (at 52126) by debbugs.gnu.org; 29 Nov 2021 20:32:58 +0000 Received: from localhost ([127.0.0.1]:39575 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mrnKY-0000sk-GU for submit@debbugs.gnu.org; Mon, 29 Nov 2021 15:32:58 -0500 Received: from eggs.gnu.org ([209.51.188.92]:51950) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mrnKV-0000sW-UX for 52126@debbugs.gnu.org; Mon, 29 Nov 2021 15:32:52 -0500 Received: from [2001:470:142:3::e] (port=59336 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mrnKP-0003os-51; Mon, 29 Nov 2021 15:32:45 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=WdW61E9dSfkDdiu/D+Fue3TkT/xXtqeDoSofiY/ASks=; b=IVtwTm578ajG K1rI73iuLrY0TKqjg1o9IFL2q/1/SXYy5WSzqBk54EMH/Q9SlLBaZsIjUboqdoew8XreVjMppJOY4 anm+P1uCW1b363xFpTi3AIkDRx3uL6v+O8N3mvZXg4ILDHZaLMZYgPVy6PgHnJLT0W6+uUmsG78wB ZVHHseprJJ0BIwOVsLZcBGpDpaxTtYcvK1iIl49Q+qV0TNkwiKccotWDMOgMWrpRS+i0JBebGCXJm RfKzOjRlqZteiClOa6egmI94zRxODPS0FBEAIOML6vV0N3JkIe3yPMxACKFzQqHX2ey8+IV8hkTOn LyEs4evbgHh6SvwfEBN97A==; Received: from [87.69.77.57] (port=2889 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mrnKO-0004sR-QB; Mon, 29 Nov 2021 15:32:45 -0500 Date: Mon, 29 Nov 2021 22:32:57 +0200 Message-Id: <837dcqvh1i.fsf@gnu.org> From: Eli Zaretskii To: Protesilaos Stavrou In-Reply-To: <87y256lo81.fsf@protesilaos.com> (message from Protesilaos Stavrou on Mon, 29 Nov 2021 22:07:58 +0200) Subject: Re: bug#52126: Problematic characters in info node names References: <871r2zueyw.fsf@gnus.org> <83ee6yvog6.fsf@gnu.org> <877dcqn8i2.fsf@protesilaos.com> <83czmivnr9.fsf@gnu.org> <871r2yn4f7.fsf@protesilaos.com> <83a6hmvj7j.fsf@gnu.org> <87y256lo81.fsf@protesilaos.com> X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 52126 Cc: 52126@debbugs.gnu.org, larsi@gnus.org, stefan@marxist.se, kyle@kyleam.com, rgm@gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) > From: Protesilaos Stavrou > Cc: larsi@gnus.org, stefan@marxist.se, 52126@debbugs.gnu.org, > kyle@kyleam.com, rgm@gnu.org > Date: Mon, 29 Nov 2021 22:07:58 +0200 > > On 2021-11-29, 21:46 +0200, Eli Zaretskii wrote: > > >> Both patches are attached. Each file name contains the Emacs version it > >> belongs to. > >> > >> I can push directly from here if you think everything is in order. > > > > Feel free to push to any of the two branches. > > > > Thanks. > > Done for both. Thank you! You should have only pushed to one of the branches, not to both. Because they are the same changes, right? From debbugs-submit-bounces@debbugs.gnu.org Mon Nov 29 15:56:46 2021 Received: (at 52126) by debbugs.gnu.org; 29 Nov 2021 20:56:46 +0000 Received: from localhost ([127.0.0.1]:39593 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mrnhZ-0001SF-R4 for submit@debbugs.gnu.org; Mon, 29 Nov 2021 15:56:46 -0500 Received: from relay9-d.mail.gandi.net ([217.70.183.199]:58315) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mrnhX-0001S1-RT for 52126@debbugs.gnu.org; Mon, 29 Nov 2021 15:56:40 -0500 Received: (Authenticated sender: public@protesilaos.com) by relay9-d.mail.gandi.net (Postfix) with ESMTPSA id 9EFAAFF809; Mon, 29 Nov 2021 20:56:31 +0000 (UTC) From: Protesilaos Stavrou To: Eli Zaretskii Subject: Re: bug#52126: Problematic characters in info node names In-Reply-To: <837dcqvh1i.fsf@gnu.org> References: <871r2zueyw.fsf@gnus.org> <83ee6yvog6.fsf@gnu.org> <877dcqn8i2.fsf@protesilaos.com> <83czmivnr9.fsf@gnu.org> <871r2yn4f7.fsf@protesilaos.com> <83a6hmvj7j.fsf@gnu.org> <87y256lo81.fsf@protesilaos.com> <837dcqvh1i.fsf@gnu.org> User-Agent: Notmuch/0.34.1 (https://notmuchmail.org) Emacs/29.0.50 (x86_64-pc-linux-gnu) Date: Mon, 29 Nov 2021 22:56:29 +0200 Message-ID: <87tufullz6.fsf@protesilaos.com> MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: -0.7 (/) X-Debbugs-Envelope-To: 52126 Cc: 52126@debbugs.gnu.org, larsi@gnus.org, stefan@marxist.se, kyle@kyleam.com, rgm@gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) On 2021-11-29, 22:32 +0200, Eli Zaretskii wrote: >> From: Protesilaos Stavrou >> Cc: larsi@gnus.org, stefan@marxist.se, 52126@debbugs.gnu.org, >> kyle@kyleam.com, rgm@gnu.org >> Date: Mon, 29 Nov 2021 22:07:58 +0200 >> >> On 2021-11-29, 21:46 +0200, Eli Zaretskii wrote: >> >> >> Both patches are attached. Each file name contains the Emacs version it >> >> belongs to. >> >> >> >> I can push directly from here if you think everything is in order. >> > >> > Feel free to push to any of the two branches. >> > >> > Thanks. >> >> Done for both. Thank you! > > You should have only pushed to one of the branches, not to both. > Because they are the same changes, right? There is a slight difference between them. The one for the master branch has an extra diff hunk which removes a single "(DIY)" from a heading. This is because emacs-28 has version 1.6.0 of the themes while master has 1.7.0. Commit 030a5c5704 on master: doc/misc/modus-themes.org | 68 +++++++++++++++++++++++------------------------ Commit ecf3bf66ba on emacs-28: doc/misc/modus-themes.org | 66 +++++++++++++++++++++++------------------------ -- Protesilaos Stavrou https://protesilaos.com From debbugs-submit-bounces@debbugs.gnu.org Mon Nov 29 22:24:59 2021 Received: (at 52126) by debbugs.gnu.org; 30 Nov 2021 03:24:59 +0000 Received: from localhost ([127.0.0.1]:39948 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mrtlH-0002dI-5f for submit@debbugs.gnu.org; Mon, 29 Nov 2021 22:24:59 -0500 Received: from eggs.gnu.org ([209.51.188.92]:51914) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mrtlF-0002d1-95 for 52126@debbugs.gnu.org; Mon, 29 Nov 2021 22:24:53 -0500 Received: from [2001:470:142:3::e] (port=47014 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mrtl8-0008FA-Mm; Mon, 29 Nov 2021 22:24:46 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=pfjEJCltxBevA8TgUb/Fbs507ZtjgYnDPN6nwGtvbu8=; b=li+E+gXHwwYU rc43ZzJVpTCscbv1Du0PduRJXGjGxJXP8HYgRvI4mr1WIMJ6EgJv9CnVrMUqVAmRrlSBNptAzPj2/ e4GWnh63CtgBcuLlyXblKGyfZL3fDC+35zpcpBQsUIB6oBDiHhpIdTGWTUPvqAdGxf+N2FUT5zXCv BXxUyh6e941gOHhhWMOa4w9chOzJgf61caxYe85srW45DAdoP+AOlzb/HgRtYZoW17W2Pk7YGc90K TRmWCnPjWc34fGC8E9veyTHQ16OwyqsQmrOdSJiAIkAI6q/OWAaqoLci8fbVMHpf6Lcwc3Gcx5Hvt rYaw4PEJ4yD/hwqg458VsQ==; Received: from [87.69.77.57] (port=4353 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mrtl8-0005am-DR; Mon, 29 Nov 2021 22:24:46 -0500 Date: Tue, 30 Nov 2021 05:25:00 +0200 Message-Id: <8335neuxyr.fsf@gnu.org> From: Eli Zaretskii To: Protesilaos Stavrou In-Reply-To: <87tufullz6.fsf@protesilaos.com> (message from Protesilaos Stavrou on Mon, 29 Nov 2021 22:56:29 +0200) Subject: Re: bug#52126: Problematic characters in info node names References: <871r2zueyw.fsf@gnus.org> <83ee6yvog6.fsf@gnu.org> <877dcqn8i2.fsf@protesilaos.com> <83czmivnr9.fsf@gnu.org> <871r2yn4f7.fsf@protesilaos.com> <83a6hmvj7j.fsf@gnu.org> <87y256lo81.fsf@protesilaos.com> <837dcqvh1i.fsf@gnu.org> <87tufullz6.fsf@protesilaos.com> X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 52126 Cc: 52126@debbugs.gnu.org, larsi@gnus.org, stefan@marxist.se, kyle@kyleam.com, rgm@gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) > From: Protesilaos Stavrou > Cc: larsi@gnus.org, stefan@marxist.se, 52126@debbugs.gnu.org, > kyle@kyleam.com, rgm@gnu.org > Date: Mon, 29 Nov 2021 22:56:29 +0200 > > >> Done for both. Thank you! > > > > You should have only pushed to one of the branches, not to both. > > Because they are the same changes, right? > > There is a slight difference between them. The one for the master > branch has an extra diff hunk which removes a single "(DIY)" from a > heading. This is because emacs-28 has version 1.6.0 of the themes while > master has 1.7.0. The common part should only be committed to one branch. Alternatively, the commit to emacs-28 should be marked with the "do not merge to master" note. See CONTRIBUTE for more about this. From debbugs-submit-bounces@debbugs.gnu.org Mon Nov 29 23:31:43 2021 Received: (at 52126) by debbugs.gnu.org; 30 Nov 2021 04:31:43 +0000 Received: from localhost ([127.0.0.1]:39998 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mrunv-0006V2-18 for submit@debbugs.gnu.org; Mon, 29 Nov 2021 23:31:43 -0500 Received: from out2.migadu.com ([188.165.223.204]:20805) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mrunr-0006Us-V3 for 52126@debbugs.gnu.org; Mon, 29 Nov 2021 23:31:41 -0500 X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kyleam.com; s=key1; t=1638246694; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=umHqIuaIXoPU31WUs2t02hkgsHs/QsdtIKcvl83LkhA=; b=SvmX1ZZ0N0mctFiveLYBYq4DB/fBhTMIC86tLnCd7p8Gb/qnrYA6tiXHdfgxMBgaEjW9rT Ho3edMvOw5dZ7537GJEvJwNY1wLvmV6ndM1a9IEr8WfGl3Ef91nl3O8cDMWcxBIhvzIRk3 XSdj5vUot+0G88Pf4LVDw22I2szH8YxFd5bxaKwoS0jZvAkcm8zyZZ1bQXDg9VZbLlMsjx UUDICe1p7J30cpnmKdd0DiyzVRwX5XK50P4CVKNQZ7cnkqCt9grWPis604Qnyk+GyqO+/H 2fmrRuEElcbor8kUWfsU5fSmUhch5AVbSXig3bH6eOIURuPQTgKkjQM1rpZ4/A== From: Kyle Meyer To: Glenn Morris , Stefan Kangas Subject: Re: bug#52126: Problematic characters in info node names In-Reply-To: <60pmqihlmr.fsf@fencepost.gnu.org> References: <871r2zueyw.fsf@gnus.org> <60pmqihlmr.fsf@fencepost.gnu.org> Date: Mon, 29 Nov 2021 23:31:30 -0500 Message-ID: <87tufue02l.fsf@kyleam.com> MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: -0.0 (/) X-Debbugs-Envelope-To: 52126 Cc: 52126@debbugs.gnu.org, Lars Ingebrigtsen , Protesilaos Stavrou X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) Glenn Morris writes: > Stefan Kangas wrote: > >> Did something change here since the above note in admin/release-process >> was written in 2013 (commit 16bcc96df4)? > > Yes. It's easy to find old versions of the Texinfo manual, eg > http://www.nongnu.org/texi2latex/texinfo/Node-Line-Requirements.html > > Newer Texinfo is less strict, but Emacs configure still claims to > support 4.13. I wonder whether 4.13 actually has a problem with the cases flagged in this issue, where the parentheses are not at the start of the text. Texinfo's ab404029d0 (parens only disallowed when looks like an external manual ref, 2011-09-18) made the following text change: @cindex Characters, invalid in node name @cindex Invalid characters in node names @cindex Node names, invalid characters in -Unfortunately, you cannot use periods, commas, colons or parentheses -within a node name; these confuse the Texinfo processors. Perhaps -this limitation will be removed some day, too. +Unfortunately, you cannot use periods, commas, or colons within a node +name; these confuse the Texinfo processors. Also, a node name may not +start with a left parenthesis and contain a right parenthesis, as in +@code{(not)allowed}; this specifies an external manual in Info. +Perhaps these limitations will be removed some day, too. That looks to be a pure documentation update to more accurately describe the restrictions. The commit message links to a thread [*] that seems to confirm that. There Patrice Dumas says What is not allowed, in reality, and leads to an error message is parentheses beginning at the beginning of the node name as you said: @node (man)bad c.texi:6: Syntax for an external node used for `(man)bad' [*] https://lists.gnu.org/archive/html/bug-texinfo/2011-09/msg00024.html From debbugs-submit-bounces@debbugs.gnu.org Mon Nov 29 23:40:03 2021 Received: (at 52126) by debbugs.gnu.org; 30 Nov 2021 04:40:03 +0000 Received: from localhost ([127.0.0.1]:40006 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mruvy-0006gX-1T for submit@debbugs.gnu.org; Mon, 29 Nov 2021 23:40:03 -0500 Received: from out0.migadu.com ([94.23.1.103]:57560) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mruvw-0006gG-4W for 52126@debbugs.gnu.org; Mon, 29 Nov 2021 23:40:01 -0500 X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kyleam.com; s=key1; t=1638247198; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=E05h4SPVvuBtAlM4gARcpTaHNOzjDvQDVteX8WLvw1w=; b=QxmEV+8onRWcDc0nIrSdIR7DurEOkN0C8c7xH9JNqpsXwl3dVw1FL2BT0z3mAXsz5WcSBD HULm1EpdMi1ST9Iklgg9ddT+dB7jE+TdN1RTWq3XnvOBdY0pLzfWagWHCfhi8ZWc2uFg/z 3Vt3qc71BplCaxaZ7k4Gz1aGT5WP3fo8kArhhlOiYMYgdpOMCBeiFB8MAIZWM7glEoN88h NN6oNvNJhPeV/QsK8SsrcqYBHPBpIWqz1ZCNrdetAzK/lNxngv66OLCmhsavl5kOgAf84i /O3x73nxDp+PsgRl2v0EBJ9L4xv+uoBMPLq49imXLydICERFs94jUQi+aL9yZw== From: Kyle Meyer To: Lars Ingebrigtsen Subject: Re: bug#52126: Problematic characters in info node names In-Reply-To: <871r2zueyw.fsf@gnus.org> References: <871r2zueyw.fsf@gnus.org> Date: Mon, 29 Nov 2021 23:39:55 -0500 Message-ID: <87sfvedzok.fsf@kyleam.com> MIME-Version: 1.0 Content-Type: text/plain X-Migadu-Flow: FLOW_OUT X-Migadu-Auth-User: kyle@kyleam.com X-Spam-Score: -0.7 (/) X-Debbugs-Envelope-To: 52126 Cc: 52126@debbugs.gnu.org, Protesilaos Stavrou , Stefan Kangas X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.7 (-) Lars Ingebrigtsen writes: > Stefan Kangas writes: > >> ** Manuals >> Check for node names using problematic characters: >> find doc -name '*.texi' -exec grep '^@node[^,]*[:.()]' {} + >> Sadly makeinfo does not warn about such characters. >> >> Running that gives me some matches: [...] >> doc/misc/org.texi:@node Hooks (2) > > And in the Org manual, so I've added Kyle to the CCs, too. Hmm, that "(2)" is being added by ox-texinfo.el's to make the node unique. As I mentioned in another message (<87tufue02l.fsf@kyleam.com>), I think these parentheses are probably okay, even for older versions of Texinfo. On the other hand, I have no objections to sidestepping the issue with something like this: diff --git a/doc/misc/org.org b/doc/misc/org.org index 85117714ee9..adf24da1c3f 100644 --- a/doc/misc/org.org +++ b/doc/misc/org.org @@ -15571,7 +15571,7 @@ ** Advanced Export Configuration :DESCRIPTION: Fine-tuning the export output. :END: -*** Hooks +*** Export hooks :PROPERTIES: :UNNUMBERED: notoc :END: @@ -18203,7 +18203,7 @@ *** Functions #+kindex: C-c C-v f Choose a file to tangle. Bound to {{{kbd(C-c C-v f)}}}. -*** Hooks +*** Tangle hooks :PROPERTIES: :UNNUMBERED: notoc :END: From debbugs-submit-bounces@debbugs.gnu.org Tue Nov 30 01:40:02 2021 Received: (at 52126) by debbugs.gnu.org; 30 Nov 2021 06:40:02 +0000 Received: from localhost ([127.0.0.1]:40056 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mrwo5-0001Ii-PH for submit@debbugs.gnu.org; Tue, 30 Nov 2021 01:40:01 -0500 Received: from mail-pf1-f179.google.com ([209.85.210.179]:39895) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mrwo3-0001IU-ID for 52126@debbugs.gnu.org; Tue, 30 Nov 2021 01:39:59 -0500 Received: by mail-pf1-f179.google.com with SMTP id i12so19578470pfd.6 for <52126@debbugs.gnu.org>; Mon, 29 Nov 2021 22:39:59 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=iu0ydPBYx/H9ZKQmJqNGnxR/lyzjjneivDAskdWN02g=; b=IQriCdvF8ZJpm5l7x/h9q6sz6gH1G/jgrxtzJ6vgsig92/f2ZSd35xz5r+Pt+bjSIk 34O4kU9KZ6/94wyUSsJUMEwvOASNdkx9lRZecE2n0lCHunTO2HJdyuW3iBiN1MPyOb21 RsNB+63rE5kT20O4jua9Y9Y1cZD2VVzX0ZnRNpAiCbcWKIOFCTWRYJ4+kBu5MEwXnv6E o6CUsM2pbX2a0WHE9S6K3mglJrFp1k+gK4Arn3n+ouFyFwDb97IhMzu4q9JC7DWiK3zj OCIIQY1D9Sc6t71RzJfrLhtQnn6ZlIi988MqZGgZd1ohzgMt9H2nC6ZoOqVdgQ6y/n6d Ydnw== X-Gm-Message-State: AOAM533w48JAwCMuyI6MmaUlhn+wd0ppjVTc3LmzaUm62vd/RSUv00EO BqocCxPXOL+Wavka8ubtuDUwIXKcodYFZ8ADI2Q= X-Google-Smtp-Source: ABdhPJwHuRLUnSf1o4Hzc5op8fhbYVDjMFc5TVHOtdonorfnmRNZfwTRLmp7gc1QYhyDSS1Qjl/iCdYQqxB1l6Nm7As= X-Received: by 2002:a05:6a00:244d:b0:44d:c279:5155 with SMTP id d13-20020a056a00244d00b0044dc2795155mr43724831pfj.0.1638254393841; Mon, 29 Nov 2021 22:39:53 -0800 (PST) Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Mon, 29 Nov 2021 22:39:53 -0800 From: Stefan Kangas In-Reply-To: <8335neuxyr.fsf@gnu.org> References: <871r2zueyw.fsf@gnus.org> <83ee6yvog6.fsf@gnu.org> <877dcqn8i2.fsf@protesilaos.com> <83czmivnr9.fsf@gnu.org> <871r2yn4f7.fsf@protesilaos.com> <83a6hmvj7j.fsf@gnu.org> <87y256lo81.fsf@protesilaos.com> <837dcqvh1i.fsf@gnu.org> <87tufullz6.fsf@protesilaos.com> <8335neuxyr.fsf@gnu.org> MIME-Version: 1.0 Date: Mon, 29 Nov 2021 22:39:53 -0800 Message-ID: Subject: Re: bug#52126: Problematic characters in info node names To: Eli Zaretskii , Protesilaos Stavrou Content-Type: text/plain; charset="UTF-8" X-Spam-Score: 0.5 (/) X-Debbugs-Envelope-To: 52126 Cc: 52126@debbugs.gnu.org, larsi@gnus.org, kyle@kyleam.com, rgm@gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -0.5 (/) Eli Zaretskii writes: > The common part should only be committed to one branch. > Alternatively, the commit to emacs-28 should be marked with the "do > not merge to master" note. See CONTRIBUTE for more about this. Yup. Otherwise, I get to resolve merge conflicts over my morning coffee. :-) There are unresolved conflicts in .../emacs/doc/misc/modus-themes.org Conflicts in: doc/misc/modus-themes.org Resolve the conflicts manually automerge: merge error It's not the end of the world, but it saves time if we can avoid it. From debbugs-submit-bounces@debbugs.gnu.org Tue Nov 30 02:16:14 2021 Received: (at 52126) by debbugs.gnu.org; 30 Nov 2021 07:16:14 +0000 Received: from localhost ([127.0.0.1]:40075 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mrxN8-0002AT-G2 for submit@debbugs.gnu.org; Tue, 30 Nov 2021 02:16:14 -0500 Received: from relay9-d.mail.gandi.net ([217.70.183.199]:36161) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mrxN5-0002AF-TI for 52126@debbugs.gnu.org; Tue, 30 Nov 2021 02:16:12 -0500 Received: (Authenticated sender: public@protesilaos.com) by relay9-d.mail.gandi.net (Postfix) with ESMTPSA id 4E449FF80E; Tue, 30 Nov 2021 07:16:03 +0000 (UTC) From: Protesilaos Stavrou To: Stefan Kangas , Eli Zaretskii Subject: Re: bug#52126: Problematic characters in info node names In-Reply-To: References: <871r2zueyw.fsf@gnus.org> <83ee6yvog6.fsf@gnu.org> <877dcqn8i2.fsf@protesilaos.com> <83czmivnr9.fsf@gnu.org> <871r2yn4f7.fsf@protesilaos.com> <83a6hmvj7j.fsf@gnu.org> <87y256lo81.fsf@protesilaos.com> <837dcqvh1i.fsf@gnu.org> <87tufullz6.fsf@protesilaos.com> <8335neuxyr.fsf@gnu.org> User-Agent: Notmuch/0.34.1 (https://notmuchmail.org) Emacs/29.0.50 (x86_64-pc-linux-gnu) Date: Tue, 30 Nov 2021 09:16:02 +0200 Message-ID: <8735neru4t.fsf@protesilaos.com> MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: -0.7 (/) X-Debbugs-Envelope-To: 52126 Cc: 52126@debbugs.gnu.org, larsi@gnus.org, kyle@kyleam.com, rgm@gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.7 (-) On 2021-11-29, 22:39 -0800, Stefan Kangas wrote: > Eli Zaretskii writes: > >> The common part should only be committed to one branch. >> Alternatively, the commit to emacs-28 should be marked with the "do >> not merge to master" note. See CONTRIBUTE for more about this. > > Yup. > > Otherwise, I get to resolve merge conflicts over my morning coffee. :-) > > There are unresolved conflicts in .../emacs/doc/misc/modus-themes.org > Conflicts in: > doc/misc/modus-themes.org > > Resolve the conflicts manually > automerge: merge error > > It's not the end of the world, but it saves time if we can avoid it. I understand, re-read CONTRIBUTE, and apologise for the inconvenience. Should I then revert the commit in master and apply to it the 1 difference I mentioned before? Just asking so that we do not commit multiple times. I noticed in 0854453ec2343cbfac3ac8e233cdc7bd2c8554a9 a pattern for how reverted commits should be written. I can follow that. -- Protesilaos Stavrou https://protesilaos.com From debbugs-submit-bounces@debbugs.gnu.org Tue Nov 30 02:41:50 2021 Received: (at 52126) by debbugs.gnu.org; 30 Nov 2021 07:41:50 +0000 Received: from localhost ([127.0.0.1]:40089 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mrxlu-0002ln-2t for submit@debbugs.gnu.org; Tue, 30 Nov 2021 02:41:50 -0500 Received: from mail-pg1-f173.google.com ([209.85.215.173]:36630) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mrxlt-0002lb-6n for 52126@debbugs.gnu.org; Tue, 30 Nov 2021 02:41:49 -0500 Received: by mail-pg1-f173.google.com with SMTP id 137so11796455pgg.3 for <52126@debbugs.gnu.org>; Mon, 29 Nov 2021 23:41:49 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=quOGqHLyZ62TObAo1yuESVmggp3fDsqt/rJvhtHXRUU=; b=Gi2RFp0wzlYRfGutZyYzXjIpxGmvsg/Mf+AJRa0Zccyqn7qAuU5UljG1vkHGRWapH6 ZorCpL1rBxDax0vMV1/E3E9QBWOuoBb3blScyck++k9ixszXWwJ2Q8N7AdytbeRI+8Ld 97oMTD+1HZEs2+2qpdH2qTI/+6vptZjO21X87/g1yLryFn3sWBofAQvtKM+N3aLC7G/k TS5qmttljDJFyPgU91elCp+FxxgZGYqZgUYesEtupY5ReONweLKbBLIJb5dfMgoAS3NL E9NyUzu1jgG2p6Q6aoH3PBaSY5g3ltfKyd3ghdgZjxKiY6ySOHkDweFZQsBECeHN0uY2 eyQw== X-Gm-Message-State: AOAM532h7bm4TImPzQcIn/Qa9Ee8qKsW7VqGU2OVsM87s/ue14UBVWh6 45nTNz0Des19nw/FtP9ULpvv0tIIyovimh966d4= X-Google-Smtp-Source: ABdhPJxO0ETDwgzJOkzpow7XwiAaxTxvfAtXYXHWsMkply2X6TskxOvD/iyxAtpTfsiRh5M97oHgylTqOitKCgczHVw= X-Received: by 2002:a62:1a03:0:b0:494:64b5:3e01 with SMTP id a3-20020a621a03000000b0049464b53e01mr45012880pfa.35.1638258103419; Mon, 29 Nov 2021 23:41:43 -0800 (PST) Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Mon, 29 Nov 2021 23:41:42 -0800 From: Stefan Kangas In-Reply-To: <8735neru4t.fsf@protesilaos.com> References: <871r2zueyw.fsf@gnus.org> <83ee6yvog6.fsf@gnu.org> <877dcqn8i2.fsf@protesilaos.com> <83czmivnr9.fsf@gnu.org> <871r2yn4f7.fsf@protesilaos.com> <83a6hmvj7j.fsf@gnu.org> <87y256lo81.fsf@protesilaos.com> <837dcqvh1i.fsf@gnu.org> <87tufullz6.fsf@protesilaos.com> <8335neuxyr.fsf@gnu.org> <8735neru4t.fsf@protesilaos.com> MIME-Version: 1.0 Date: Mon, 29 Nov 2021 23:41:42 -0800 Message-ID: Subject: Re: bug#52126: Problematic characters in info node names To: Protesilaos Stavrou , Eli Zaretskii Content-Type: text/plain; charset="UTF-8" X-Spam-Score: 0.5 (/) X-Debbugs-Envelope-To: 52126 Cc: 52126@debbugs.gnu.org, larsi@gnus.org, kyle@kyleam.com, rgm@gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -0.5 (/) Protesilaos Stavrou writes: > I understand, re-read CONTRIBUTE, and apologise for the inconvenience. No need to apologize. It happens! > Should I then revert the commit in master and apply to it the 1 > difference I mentioned before? Just asking so that we do not commit > multiple times. It's better to just leave it alone for now, as it's already been merged to master. From debbugs-submit-bounces@debbugs.gnu.org Tue Nov 30 11:48:40 2021 Received: (at 52126) by debbugs.gnu.org; 30 Nov 2021 16:48:40 +0000 Received: from localhost ([127.0.0.1]:42253 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ms6J6-0003sT-AL for submit@debbugs.gnu.org; Tue, 30 Nov 2021 11:48:40 -0500 Received: from eggs.gnu.org ([209.51.188.92]:50370) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ms6J1-0003s8-0I for 52126@debbugs.gnu.org; Tue, 30 Nov 2021 11:48:38 -0500 Received: from [2001:470:142:3::e] (port=39500 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ms6Iv-0005ZM-BR; Tue, 30 Nov 2021 11:48:29 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=skYU99uTREwO/3lGMV8CKaH7v61cr0SAx+JriSkHOxM=; b=nkZCkNZbqehb RKMSH5jgxKHuFHKnXYxmsVtx8be10XQfE2/jOU9q45LPXQgz3u52I6exSBo43qsWxj61cWti4WeHM hvJZBu8RS7uacX8yOkhE23V7+R2gknO7dmNIMf0br3iBBhHgY9a0c6grstbdUuxDmUEAT1DGxV63a FDamT/ioSpl94CKoO79B7jAwGXy/X/o2XkzioFVkIAfq7R99bilbAi+e1h8Pm6lCiqT7pNe+bdQgc S3wEx8xbcHdxq7BZ+9K1KGtYUNpZ+l0exlKXAE5jqKlOAZSkEUhK+YZV1VP7kj+of/EjoIC3+dSNz TdyWwSndxTJP+pd/8+itlA==; Received: from [87.69.77.57] (port=2070 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ms6Iv-0005oP-24; Tue, 30 Nov 2021 11:48:29 -0500 Date: Tue, 30 Nov 2021 18:48:44 +0200 Message-Id: <83wnkptwr7.fsf@gnu.org> From: Eli Zaretskii To: Protesilaos Stavrou In-Reply-To: <8735neru4t.fsf@protesilaos.com> (message from Protesilaos Stavrou on Tue, 30 Nov 2021 09:16:02 +0200) Subject: Re: bug#52126: Problematic characters in info node names References: <871r2zueyw.fsf@gnus.org> <83ee6yvog6.fsf@gnu.org> <877dcqn8i2.fsf@protesilaos.com> <83czmivnr9.fsf@gnu.org> <871r2yn4f7.fsf@protesilaos.com> <83a6hmvj7j.fsf@gnu.org> <87y256lo81.fsf@protesilaos.com> <837dcqvh1i.fsf@gnu.org> <87tufullz6.fsf@protesilaos.com> <8335neuxyr.fsf@gnu.org> <8735neru4t.fsf@protesilaos.com> X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 52126 Cc: 52126@debbugs.gnu.org, larsi@gnus.org, stefan@marxist.se, kyle@kyleam.com, rgm@gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) > From: Protesilaos Stavrou > Cc: larsi@gnus.org, 52126@debbugs.gnu.org, kyle@kyleam.com, rgm@gnu.org > Date: Tue, 30 Nov 2021 09:16:02 +0200 > > I noticed in 0854453ec2343cbfac3ac8e233cdc7bd2c8554a9 a pattern for how > reverted commits should be written. I can follow that. You don't have to: the pattern is produced by Git itself, and if you want to add or change something, invoke "git revert -e". From debbugs-submit-bounces@debbugs.gnu.org Thu Dec 02 20:12:32 2021 Received: (at 52126-done) by debbugs.gnu.org; 3 Dec 2021 01:12:32 +0000 Received: from localhost ([127.0.0.1]:49736 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1msx7o-00061c-57 for submit@debbugs.gnu.org; Thu, 02 Dec 2021 20:12:32 -0500 Received: from mail-pj1-f54.google.com ([209.85.216.54]:36500) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1msx7k-000617-1W for 52126-done@debbugs.gnu.org; Thu, 02 Dec 2021 20:12:30 -0500 Received: by mail-pj1-f54.google.com with SMTP id n15-20020a17090a160f00b001a75089daa3so3908824pja.1 for <52126-done@debbugs.gnu.org>; Thu, 02 Dec 2021 17:12:28 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:in-reply-to:references:user-agent :mime-version:date:message-id:subject:to:cc; bh=h7IJuEZqypFrf3q7wQnnRIDhzAuWrEp5/5Ga2KwcSoY=; b=JIVe49l1NCGtc1u/JaEToPuAH62JMVlPH/guE69KnH1DbVEUkMeqViGEIX93jK7AdI hehdWytber78iVBEpcmHgimobSLFOo54kIMzCMR4m24JlAiOxdiPPbqgFoHvRicc/QLK pw64X5dAyjuUmzDsC3r8OJsljays45PAPpw9u6OBzHBSWC8U+v7ZfUbMFlJBFkx8PtWg +MhNPM3v6ZZ6mscERkbJMg9wHwenzTAjpcz3ZGTQqOStns0nanV2jFYQ+lR75biYQ359 eeAlIyQZ2spips/wwwoDnfNA6ZWRd8ySJUSje6450gTsud/oq4c6n6mI2ExrBaX1D1N5 s8sQ== X-Gm-Message-State: AOAM533c0yVVZANRbt6o+YELu82JIP0H4BFz6TzhngeWovg9GIDOxtre kDt+5tsFP1yKDWYnhzjme16vAbveTuL3iJcFvrXCl/kc X-Google-Smtp-Source: ABdhPJzZARUeA/Kk8ZQ/iPv6o0w9GcgaDXPO5BxfoBNEWbWk2iLnznINEHTNdnDWflDMHFbQbkAyUVJLg2EFK6338HU= X-Received: by 2002:a17:90a:be10:: with SMTP id a16mr9961519pjs.133.1638493942426; Thu, 02 Dec 2021 17:12:22 -0800 (PST) Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Thu, 2 Dec 2021 17:12:22 -0800 From: Stefan Kangas In-Reply-To: <87sfvedzok.fsf@kyleam.com> (Kyle Meyer's message of "Mon, 29 Nov 2021 23:39:55 -0500") References: <871r2zueyw.fsf@gnus.org> <87sfvedzok.fsf@kyleam.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) MIME-Version: 1.0 Date: Thu, 2 Dec 2021 17:12:22 -0800 Message-ID: Subject: Re: bug#52126: Problematic characters in info node names To: Kyle Meyer Content-Type: text/plain; charset="UTF-8" X-Spam-Score: 0.5 (/) X-Debbugs-Envelope-To: 52126-done Cc: Lars Ingebrigtsen , 52126-done@debbugs.gnu.org, Protesilaos Stavrou X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -0.5 (/) Kyle Meyer writes: > Hmm, that "(2)" is being added by ox-texinfo.el's to make the node > unique. As I mentioned in another message > (<87tufue02l.fsf@kyleam.com>), I think these parentheses are probably > okay, even for older versions of Texinfo. > > On the other hand, I have no objections to sidestepping the issue with > something like this: Thanks, that looks like a reasonable fix. None of this seems urgent to me, so I'd suggest you consider pushing that fix to the Org-mode repository and we will eventually get it merged into Emacs in the normal way. With that, I'm closing this bug as it seems the issues here are resolved. Thanks. From debbugs-submit-bounces@debbugs.gnu.org Thu Dec 02 20:45:37 2021 Received: (at 52126-done) by debbugs.gnu.org; 3 Dec 2021 01:45:37 +0000 Received: from localhost ([127.0.0.1]:49771 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1msxdm-0002q1-L1 for submit@debbugs.gnu.org; Thu, 02 Dec 2021 20:45:37 -0500 Received: from out2.migadu.com ([188.165.223.204]:53169) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1msxdg-0002po-I0 for 52126-done@debbugs.gnu.org; Thu, 02 Dec 2021 20:45:32 -0500 X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kyleam.com; s=key1; t=1638495927; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=pq497iWsC23MSUFA1UzHB01agWvBZ1Z6/iojDqshphk=; b=MVjvW/cxlTrTDCZwXfc5eJmqAVrowIi88HFgy+oRFwN1nxS/yvuJAkIYwsgFnqhcY3cC1h /+e/m25ug21OjEsvd0B9WDMZZONP7o8U+N2QHg4Xd9fyxawjvV3Oyataob2v1sCubcpT6n a3unbiNkUc+9M4t1AghioD9RvXnLme874HhYlWSq1bOqr2sQ7/atR9qgVjYDWwQnTwsVGI KidGmDPKXYJopbUCxsYKg3X+jC93SQsM6/klGIhRib5azI8R2xyQlGM7v69nyoKtIfOkmx eOJ7QF5bpNu9EKgfxxT/hxSNEnIWUQTpnVU6kBtCwR4meSK4bS/0Hv+EM3V64w== From: Kyle Meyer To: Stefan Kangas Subject: Re: bug#52126: Problematic characters in info node names In-Reply-To: References: <871r2zueyw.fsf@gnus.org> <87sfvedzok.fsf@kyleam.com> Date: Thu, 02 Dec 2021 20:45:18 -0500 Message-ID: <87v9065ump.fsf@kyleam.com> MIME-Version: 1.0 Content-Type: text/plain X-Migadu-Flow: FLOW_OUT X-Migadu-Auth-User: kyleam.com X-Spam-Score: -0.0 (/) X-Debbugs-Envelope-To: 52126-done Cc: Lars Ingebrigtsen , 52126-done@debbugs.gnu.org, Protesilaos Stavrou X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) Stefan Kangas writes: > Thanks, that looks like a reasonable fix. None of this seems urgent to > me, so I'd suggest you consider pushing that fix to the Org-mode > repository and we will eventually get it merged into Emacs in the normal > way. Pushed to the Org repo (0acd2fed2). From unknown Fri Aug 15 20:54:49 2025 Received: (at fakecontrol) by fakecontrolmessage; To: internal_control@debbugs.gnu.org From: Debbugs Internal Request Subject: Internal Control Message-Id: bug archived. Date: Fri, 31 Dec 2021 12:24:05 +0000 User-Agent: Fakemail v42.6.9 # This is a fake control message. # # The action: # bug archived. thanks # This fakemail brought to you by your local debbugs # administrator