From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on archive.lwn.net X-Spam-Level: X-Spam-Status: No, score=-5.8 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI autolearn=ham autolearn_force=no version=3.4.1 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by archive.lwn.net (Postfix) with ESMTP id 17F527DE78 for ; Thu, 10 May 2018 16:51:10 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S966267AbeEJQvJ (ORCPT ); Thu, 10 May 2018 12:51:09 -0400 Received: from ms.lwn.net ([45.79.88.28]:58112 "EHLO ms.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965017AbeEJQvI (ORCPT ); Thu, 10 May 2018 12:51:08 -0400 Received: from localhost.localdomain (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ms.lwn.net (Postfix) with ESMTPSA id A0A61318; Thu, 10 May 2018 16:51:07 +0000 (UTC) Date: Thu, 10 May 2018 10:51:05 -0600 From: Jonathan Corbet To: Matthew Wilcox Cc: Mauro Carvalho Chehab , Mauro Carvalho Chehab , Christoph Hellwig , Linux Doc Mailing List , linux-kernel@vger.kernel.org, Ingo Molnar , Peter Zijlstra Subject: Re: [RFC PATCH 1/2] scripts/kernel-doc: Auto-detect common code-blocks Message-ID: <20180510105105.5cb0d54f@lwn.net> In-Reply-To: <20180510163456.GC30442@bombadil.infradead.org> References: <2ac6e3da22119f714406925139e40f4d835d11a4.1525962971.git.mchehab+samsung@kernel.org> <20180510163456.GC30442@bombadil.infradead.org> Organization: LWN.net X-Mailer: Claws Mail 3.15.1-dirty (GTK+ 2.24.32; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Sender: linux-doc-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-doc@vger.kernel.org On Thu, 10 May 2018 09:34:56 -0700 Matthew Wilcox wrote: > I think this is a bit fragile. Why not just search for ':\n'? Is > there ever a case where we want to write: > > /** > * foo is a bar: > * wibble > */ > and have wibble not be a code-block? Yeah, we might want to write something like: - Leading off a bulleted list 1) or a numbered list for example. That's why I was thinking of looking for explicit markers for such lists. It'll take some playing around with to have a hope of getting right, methinks. jon -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html