From: peterz@infradead.org
To: Vegard Nossum <vegard.nossum@oracle.com>
Cc: NeilBrown <neilb@suse.de>, Steven Rostedt <rostedt@goodmis.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Re: Minor RST rant
Date: Wed, 5 Aug 2020 17:12:30 +0200 [thread overview]
Message-ID: <20200805151230.GT2674@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <1e60ff85-4965-92cb-e50b-8ea9ccf6788e@oracle.com>
On Wed, Aug 05, 2020 at 04:49:50PM +0200, Vegard Nossum wrote:
> FWIW, I *really* like how the extra markup renders in a browser, and I
> don't think I'm the only one.
The thing is, I write code in a text editor, not a browser. When a
header file says: read Documentation/foo I do 'gf' and that file gets
opened in a buffer.
Needing a browser is a fail.
> If you want to read .rst files in a terminal, I would suggest using
> something like this:
>
> $ pandoc -t plain Documentation/core-api/atomic_ops.rst | less
That doesn't help me with people sending me that abysmal shite in diff
format.
next prev parent reply other threads:[~2020-08-05 20:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 17:22 Minor RST rant Steven Rostedt
2020-07-24 17:33 ` Jonathan Corbet
2020-07-24 18:42 ` Steven Rostedt
2020-07-24 23:46 ` NeilBrown
2020-07-29 12:44 ` peterz
2020-08-05 14:49 ` Vegard Nossum
2020-08-05 15:12 ` peterz [this message]
2020-08-06 6:48 ` Christoph Hellwig
2020-08-06 8:36 ` Vegard Nossum
2020-07-28 12:52 ` peterz
2020-07-28 15:28 ` Steven Rostedt
2020-07-29 9:36 ` peterz
2020-07-24 17:41 ` Matthew Wilcox
2020-07-24 18:14 ` David Sterba
2020-07-24 18:51 ` Steven Rostedt
2020-07-24 23:58 ` NeilBrown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200805151230.GT2674@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=rostedt@goodmis.org \
--cc=vegard.nossum@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.