docs.lists.yoctoproject.org archive mirror
 help / color / mirror / Atom feed
* did we ever resolve whether sphinx supported "replaceable" markup?
@ 2021-09-01  8:56 Robert P. J. Day
  2021-09-01  9:04 ` [docs] " Nicolas Dechesne
  0 siblings, 1 reply; 2+ messages in thread
From: Robert P. J. Day @ 2021-09-01  8:56 UTC (permalink / raw)
  To: YP docs mailing list


  longer ago than i care to remember, i mentioned that one thing i
missed about docbook was the notion of the <replaceable> markup, which
emphasized that something was merely a placeholder for an actual
value -- this was normally rendered in italics.

  i ask since it would be nice to have the same thing, since in the
dev manual i am currently proofing, there's this code snippet:

  $ source oe-init-build-env [build_dir]

where "[]" is clearly meant to imply replaceable, and yet, only a few
lines further down:

  $ bitbake target

where "target" is also clearly meant to be replaceable, but there is
no markup to imply that, so it's kind of inconsistent.

  i'm guessing there's no easy way to do this, other than perhaps to
define another sphinx directive if it seems worth it.

rday

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [docs] did we ever resolve whether sphinx supported "replaceable" markup?
  2021-09-01  8:56 did we ever resolve whether sphinx supported "replaceable" markup? Robert P. J. Day
@ 2021-09-01  9:04 ` Nicolas Dechesne
  0 siblings, 0 replies; 2+ messages in thread
From: Nicolas Dechesne @ 2021-09-01  9:04 UTC (permalink / raw)
  To: Robert P. J. Day; +Cc: YP docs mailing list

On Wed, Sep 1, 2021 at 10:56 AM Robert P. J. Day <rpjday@crashcourse.ca> wrote:
>
>
>   longer ago than i care to remember, i mentioned that one thing i
> missed about docbook was the notion of the <replaceable> markup, which
> emphasized that something was merely a placeholder for an actual
> value -- this was normally rendered in italics.

This is the discussion you are referring to here:
https://lists.yoctoproject.org/g/docs/topic/77954380#567

It remains a good idea, and I am not aware of anything done since. It
is potentially something that could be brought up with the Sphinx
community as it is a generic question that might be interesting much
beyond our use cases.


>
>   i ask since it would be nice to have the same thing, since in the
> dev manual i am currently proofing, there's this code snippet:
>
>   $ source oe-init-build-env [build_dir]
>
> where "[]" is clearly meant to imply replaceable, and yet, only a few
> lines further down:
>
>   $ bitbake target
>
> where "target" is also clearly meant to be replaceable, but there is
> no markup to imply that, so it's kind of inconsistent.
>
>   i'm guessing there's no easy way to do this, other than perhaps to
> define another sphinx directive if it seems worth it.
>
> rday
>
> 
>

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2021-09-01  9:04 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-09-01  8:56 did we ever resolve whether sphinx supported "replaceable" markup? Robert P. J. Day
2021-09-01  9:04 ` [docs] " Nicolas Dechesne

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).