From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.4 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED, T_SCC_BODY_TEXT_LINE,UNPARSEABLE_RELAY autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 27159 invoked from network); 19 May 2022 04:27:37 -0000 Received: from zero.zsh.org (2a02:898:31:0:48:4558:7a:7368) by inbox.vuxu.org with ESMTPUTF8; 19 May 2022 04:27:37 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=zsh.org; s=rsa-20210803; h=List-Archive:List-Owner:List-Post:List-Unsubscribe: List-Subscribe:List-Help:List-Id:Sender:Content-Transfer-Encoding: Content-Type:Subject:Cc:To:From:Date:References:In-Reply-To:Message-Id: Mime-Version:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID; bh=lZ9CtFPdBrrDQrkTlSEkK9PvQ7SGup6K0y1pv+A0mvs=; b=bOdSYGaJXLweRt+XEgi1KDzM9T /GQEiGRMKu1ZvWmDeGhN6fYxSu6q5cMBYLZj8iMAK2MNsoyOYBXSgqmHwrQqM3S1RMfm1TFisyn5q 4z9D1UJ+Zx955As5Zzb2WtnFcTvaxEgHNMsbck7rODjn1wmdFjf4D3JWOLQutHztrC+Cyo6FOKbLp CcAAJZDh1qwbbdIvKhDGq7DSLE9Rn03dAfB/oA3a08umwuRyn6uQ5LoQ2iF6gvhMu0x/z/CAbLuRZ V4cuRaNL/OFAtXBq0mJF+TKjDQrpnPh0hOM5QjGc812Z9GEF31L15b7JNpHYDsFlXsMUmjwro3GiM zgY6toGg==; Received: from authenticated user by zero.zsh.org with local id 1nrXlA-000EOx-6u; Thu, 19 May 2022 04:27:36 +0000 Received: from authenticated user by zero.zsh.org with esmtpsa (TLS1.3:TLS_AES_256_GCM_SHA384:256) id 1nrXkv-000E3h-KB; Thu, 19 May 2022 04:27:21 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailauth.nyi.internal (Postfix) with ESMTP id F1C3127C0054; Thu, 19 May 2022 00:27:19 -0400 (EDT) Received: from imap48 ([10.202.2.98]) by compute2.internal (MEProxy); Thu, 19 May 2022 00:27:19 -0400 X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedriedtgdekgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvvefutgfgsehtqhertderreejnecuhfhrohhmpefnrgif rhgvnhgtvggpgggvlhojiihquhgviicuoehlrghrrhihvhesiihshhdrohhrgheqnecugg ftrfgrthhtvghrnheptdethfevgeettdfgueefuddtheefjeehffffuddvueekhfetffdv tdfhveeggeegnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homheplhgrrhhrhihvodhmvghsmhhtphgruhhthhhpvghrshhonhgrlhhithihqdduudeh udekjeejtdegqdduudelvdejfeekhedqlhgrrhhrhihvpeepiihshhdrohhrghesfhgrsh htmhgrihhlrdgtohhm X-ME-Proxy: Feedback-ID: iaa214773:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id 43EC031A005D; Thu, 19 May 2022 00:27:19 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.7.0-alpha0-591-gfe6c3a2700-fm-20220427.001-gfe6c3a27 Mime-Version: 1.0 Message-Id: In-Reply-To: References: <33e425a1-36a6-4fa6-8a59-a892a7861d93@www.fastmail.com> Date: Thu, 19 May 2022 00:26:59 -0400 From: =?UTF-8?Q?Lawrence_Vel=C3=A1zquez?= To: dana Cc: zsh-workers@zsh.org, "Bevan Stanely" Subject: Re: Proposal: Use Markdown syntax for README and other documentation Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Seq: 50248 Archived-At: X-Loop: zsh-workers@zsh.org Errors-To: zsh-workers-owner@zsh.org Precedence: list Precedence: bulk Sender: zsh-workers-request@zsh.org X-no-archive: yes List-Id: List-Help: List-Subscribe: List-Unsubscribe: List-Post: List-Owner: List-Archive: On Thu, May 19, 2022, at 12:02 AM, dana wrote: > On Wed 18 May 2022, at 20:10, Lawrence Vel=C3=A1zquez wrote: >> While nice for editing, raw markup (even Markdown) makes for a poor >> reading experience. > > I don't think that's necessarily the case, as demonstrated by the fact > that Bevan thought we were already using Markdown lol. And we very nea= rly > are I agree that Markdown is not bad if limited to the quieter markup (e.g., headings, strong, emphasis, lists, blockquotes, etc.). Those also tend to be decently portable between implementations. The problem is that it's always tempting to move on to the less-quiet markup :-/ > I don't think it'd be a big change to have the README standardise on s= ome > sub-set of Markdown to make it look a little nicer on code-hosting sit= es, > as long as we continued to avoid the more advanced/noisy features like > images and hyper-links The PR in question introduces both of those things, as well as raw HTML (which SourceForge would sanitize away) and backslash escaping. --=20 vq