Re: [Rfc-markdown] [netmod] too long lines from IANA module inclusion
Carsten Bormann <cabo@tzi.org> Fri, 17 December 2021 17:12 UTC
Return-Path: <cabo@tzi.org>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFACE3A0866; Fri, 17 Dec 2021 09:12:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KhByEFKaFFht; Fri, 17 Dec 2021 09:12:48 -0800 (PST)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 700883A086F; Fri, 17 Dec 2021 09:12:47 -0800 (PST)
Received: from [192.168.217.118] (p5089a436.dip0.t-ipconnect.de [80.137.164.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4JFwXW6gzHzDCbW; Fri, 17 Dec 2021 18:12:43 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <0100017dc93be244-843adcee-efda-49d4-9814-fbf91153126b-000000@email.amazonses.com>
Date: Fri, 17 Dec 2021 18:12:43 +0100
Cc: "netmod@ietf.org" <netmod@ietf.org>, Benoit Claise <benoit.claise=40huawei.com@dmarc.ietf.org>, Slavomír Mazúr <Slavomir.Mazur@pantheon.tech>, Miroslav Kováč <miroslav.kovac@pantheon.tech>, rfc-markdown@ietf.org, Michael Richardson <mcr+ietf@sandelman.ca>, "Eric Vyncke (evyncke)" <evyncke@cisco.com>
X-Mao-Original-Outgoing-Id: 661453963.289202-ad4f3007dc7d02d7e7014cc53b683a28
Content-Transfer-Encoding: quoted-printable
Message-Id: <9B95F768-DA2B-48CA-A66F-F406AECFCE08@tzi.org>
References: <43BBAD20-D816-4D01-8326-1D67185CCC19@tzi.org> <24856.1639347093@localhost> <0100017db6a106f8-a9773885-6347-4fd6-a2d6-69ec6941bc7b-000000@email.amazonses.com> <20211214.083324.1824911592330241723.id@4668.se> <3782772c-b5b4-4285-f65e-67b1113e1b07@huawei.com> <0100017dc8e0fcbd-8899bb50-f0bf-4537-a87b-64eb82d9664a-000000@email.amazonses.com> <FB6407ED-BA9D-415A-AFCB-0D4D327679ED@tzi.org> <0100017dc93be244-843adcee-efda-49d4-9814-fbf91153126b-000000@email.amazonses.com>
To: Kent Watsen <kent@watsen.net>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/Qbiase7RWeJAmxLYhMgtheni3No>
Subject: Re: [Rfc-markdown] [netmod] too long lines from IANA module inclusion
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Dec 2021 17:12:53 -0000
On 2021-12-17, at 17:31, Kent Watsen <kent@watsen.net> wrote: > >> Examples from the HTTP ecosystem (GNAP, HTTPAPI, HTTPBIS) didn’t have any “===“ decoration, though. (Why the heck was this left open as a choice for the author? I like “%%%” decoration instead, should I use that as a personal fashion statement?) > > Because sometimes it is desirable for the bracketing to match the native file commenting syntax (e.g., “#“ for shell/Python, “//“ for C++, “;” for ABNF, etc.) But those tools never see that header. (Or are there examples where you can safely feed a folded block to a tool?) Grüße, Carsten
- Re: [Rfc-markdown] [netmod] too long lines from I… Carsten Bormann
- Re: [Rfc-markdown] [netmod] too long lines from I… Kent Watsen
- Re: [Rfc-markdown] [netmod] too long lines from I… Carsten Bormann
- Re: [Rfc-markdown] [netmod] too long lines from I… Kent Watsen
- Re: [Rfc-markdown] [netmod] too long lines from I… Mark Nottingham
- Re: [Rfc-markdown] [netmod] too long lines from I… Carsten Bormann