linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "André Almeida" <andrealmeid@collabora.com>, linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, corbet@lwn.net,
	kernel@collabora.com, "André Almeida" <andrealmeid@collabora.com>
Subject: Re: [PATCH] sphinx.rst: Add note about code snippets embedded in the text
Date: Wed, 12 Jun 2019 10:57:12 +0300	[thread overview]
Message-ID: <87ftofxmlj.fsf@intel.com> (raw)
In-Reply-To: <20190611200316.30054-1-andrealmeid@collabora.com>

On Tue, 11 Jun 2019, André Almeida <andrealmeid@collabora.com> wrote:
> There's a paragraph that explains how to create fixed width text block,
> but it doesn't explains how to create fixed width text inline, although
> this feature is really used through the documentation. Fix that adding a
> quick note about it.

I don't mind this addition, it's simple enough, but in general I think
we should reference the Sphinx and reStructuredText documentation,
whichever is more applicable, instead of duplicating the
documentation. The idea is that this document describes how to use them
in kernel. Contrast with coding style and language reference.

BR,
Jani.


>
> Signed-off-by: André Almeida <andrealmeid@collabora.com>
> ---
>  Documentation/doc-guide/sphinx.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/doc-guide/sphinx.rst b/Documentation/doc-guide/sphinx.rst
> index c039224b404e..f48abc07f4c5 100644
> --- a/Documentation/doc-guide/sphinx.rst
> +++ b/Documentation/doc-guide/sphinx.rst
> @@ -218,7 +218,7 @@ Here are some specific guidelines for the kernel documentation:
>    examples, etc.), use ``::`` for anything that doesn't really benefit
>    from syntax highlighting, especially short snippets. Use
>    ``.. code-block:: <language>`` for longer code blocks that benefit
> -  from highlighting.
> +  from highlighting. For a short snippet of code embedded in the text, use \`\`.
>  
>  
>  the C domain

-- 
Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2019-06-12  7:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-11 20:03 [PATCH] sphinx.rst: Add note about code snippets embedded in the text André Almeida
2019-06-12  7:57 ` Jani Nikula [this message]
2019-06-14 20:39 ` Jonathan Corbet

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=87ftofxmlj.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=andrealmeid@collabora.com \
    --cc=corbet@lwn.net \
    --cc=kernel@collabora.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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).