From: Vegard Nossum <vegard.nossum@oracle.com>
To: Christoph Hellwig <hch@infradead.org>, peterz@infradead.org
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: Minor RST rant
Date: Thu, 6 Aug 2020 10:36:17 +0200 [thread overview]
Message-ID: <d739e7e1-4eca-b927-1df8-dd04bec3b85e@oracle.com> (raw)
In-Reply-To: <20200806064823.GA7292@infradead.org>
On 2020-08-06 08:48, Christoph Hellwig wrote:
> On Wed, Aug 05, 2020 at 05:12:30PM +0200, peterz@infradead.org wrote:
>> 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.
>
> And that is my main problem with all the RST craze. It optmizes for
> shiny display in a browser, but copletely messed up the typical
> developer flow.
>
If you are using vim, you can put this in ~/.vim/after/syntax/rst.vim:
syn region rstInlineLiteral matchgroup=Special start="``" end="``"
concealends
syn region rstEmphasis matchgroup=Special start="\*\*" end="\*\*"
concealends
setlocal conceallevel=2
This will hide the ``foo`` and **bar** markup on lines that are not
currently under the cursor.
Vegard
next prev parent reply other threads:[~2020-08-06 11: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
2020-08-06 6:48 ` Christoph Hellwig
2020-08-06 8:36 ` Vegard Nossum [this message]
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=d739e7e1-4eca-b927-1df8-dd04bec3b85e@oracle.com \
--to=vegard.nossum@oracle.com \
--cc=corbet@lwn.net \
--cc=hch@infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).