Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754746AbcK1Ly0 (ORCPT ); Mon, 28 Nov 2016 06:54:26 -0500 Received: from bombadil.infradead.org ([198.137.202.9]:33181 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754036AbcK1LyS (ORCPT ); Mon, 28 Nov 2016 06:54:18 -0500 Date: Mon, 28 Nov 2016 12:54:13 +0100 From: Peter Zijlstra To: Mauro Carvalho Chehab Cc: Jonathan Corbet , Silvio Fricke , linux-doc@vger.kernel.org, Ming Lei , "Luis R . Rodriguez" , Mauro Carvalho Chehab , linux-kernel@vger.kernel.org, Jani Nikula Subject: Re: [PATCH v3 2/4] Documentation/atomic_ops.txt: convert to ReST markup Message-ID: <20161128115413.GW3092@twins.programming.kicks-ass.net> References: <20161125215814.GA3061@worktop.programming.kicks-ass.net> <20161127165914.5b84cc65@lwn.net> <20161128072626.GT3092@twins.programming.kicks-ass.net> <20161128084442.uqfcar5qx2b7u34v@phenom.ffwll.local> <20161128102009.GV3092@twins.programming.kicks-ass.net> <20161128090855.589f9357@vento.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161128090855.589f9357@vento.lan> User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1306 Lines: 35 On Mon, Nov 28, 2016 at 09:08:55AM -0200, Mauro Carvalho Chehab wrote: > - use *foo* (for italics) or **foo** (for bold) instead of _foo_; That's daft, and also you're wrong. The normal convention is: /italic/ *bold* _underlined_ > :ref:`Documentation/admin-guide/serial-console.rst ` That seems to work, as in 'gf' doesn't get confused by the spurious characters attached. Is there any way to enforce that? > - if you have something that you want to use a monotonic font on > PDF/LaTeX/HTML, use ``foo``. Bit weird, somewhere in the typewriter age they invented the " symbol so we didn't have to type double quotes anymore. > - if you use special characters like '*' in the middle of the text > (outsize a literal block), prepend with a \ in order to escape > parsing it. That's a bit inconvenient I suppose. > Btw, a lot of editors recognize ReST files and are capable of > parsing the ReST tags while displaying the file, including vim > and emacs, using different colors and/or bold to display those tags. > So, even for text-editing, converting to ReST brings improvements. Doesn't seem to really work though; if I open Documentation/development-process/1.Intro.rst the :ref:s at the start of the document don't work with the regular 'follow-ref' key combo of ^].