From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: tydrdn Newsgroups: gmane.emacs.devel Subject: Re: Indentation conventions for Info manuals; recognizing code Date: Mon, 08 Mar 2021 09:51:25 +0000 Message-ID: Reply-To: tydrdn Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="29497"; mail-complaints-to="usenet@ciao.gmane.io" To: "emacs-devel@gnu.org" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Mar 08 10:53:02 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lJCZR-0007ZY-Td for ged-emacs-devel@m.gmane-mx.org; Mon, 08 Mar 2021 10:53:01 +0100 Original-Received: from localhost ([::1]:47050 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lJCZQ-0003Gt-U9 for ged-emacs-devel@m.gmane-mx.org; Mon, 08 Mar 2021 04:53:00 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58120) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lJCYB-0002LK-Q5 for emacs-devel@gnu.org; Mon, 08 Mar 2021 04:51:43 -0500 Original-Received: from mail-40130.protonmail.ch ([185.70.40.130]:42371) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lJCY8-0004v6-EZ for emacs-devel@gnu.org; Mon, 08 Mar 2021 04:51:43 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail; t=1615197096; bh=atzzgpkJP6mheGf/P2PBCnYkOOAUjCQIKj0dWc1TNwM=; h=Date:To:From:Reply-To:Subject:From; b=Zo07Y/cEr4vcvm3sXNtlRx9yYK41nNSmfxQdfsqiR8YwFkMa3fMmCdoPVBzPbRRGN 9TA8NKqyrC+YHH8gSYeBb0exf2Y05ffaoEnHJfGv/zuW4DycBqAYD/ZP10gXF18Ztj ZK+9kxNjIUt5kztigGmvuajefxFpk2+sJCM3UXsE= Received-SPF: pass client-ip=185.70.40.130; envelope-from=laszlomail@protonmail.com; helo=mail-40130.protonmail.ch X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:266168 Archived-At: > So if some kind of "code" marker would be retained > in the Info output, it would need to be implemented in the 2 or 3 > other Info readers out there, not just in Emacs. makeinfo could have a new option to add separators for the generated code examples, something like: --- example begin .... --- example end This is just text, so others info readers could display it as is, while emacs could use the separators to recognize code sections.