Date: Thu, 20 Feb 2014 07:57:47 -0700 (MST) From: Warren Block <wblock@wonkity.com> To: Hiroki Sato <hrs@FreeBSD.org> Cc: freebsd-doc@FreeBSD.org, freebsd@allanjude.com Subject: Re: ZFS handbook project patch Message-ID: <alpine.BSF.2.00.1402200747110.69044@wonkity.com> In-Reply-To: <20140220.162055.109321178462259649.hrs@allbsd.org> References: <5305A9A4.1010603@allanjude.com> <20140220.162055.109321178462259649.hrs@allbsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 20 Feb 2014, Hiroki Sato wrote:
> Allan Jude <freebsd@allanjude.com> wrote
> in <5305A9A4.1010603@allanjude.com>:
>
> fr> It also fixes a paragraph that someone else wrote, that Warren had
> fr> pointed out made no sense.
> fr>
> fr> Also adds some missing <acronym> tags, and replace all of the
> fr> <userinput> tags that are actually commands with <command>
>
> - <screen>&prompt.root; <userinput>service zfs start</userinput></screen>
> + <screen>&prompt.root; <command>service zfs start</command></screen>
>
> <userinput> is correct here. <command> is for the name of an
> executable program or command, not a command line.
Yes. Although <command> is sometimes used for short inline commands
that are a bit more than a simple command name:
<para>Files beginning with the letter "A" can be listed with
<command>ls A*</command>. More detailed searches can be done with
<command>find</command>:</para>
<screen>&prompt.user; <userinput>find /usr/ports -name Makefile</userinput></screen>
There are some examples in the FDP Primer:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/book.html#idp66516784
(Although they also show <prompt>, which I don't recall seeing used
anywhere else in our docs and am pretty sure I've never used myself.)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1402200747110.69044>