[systemd-devel] [PATCH] s/commandline/command line/g

[Jason St. John]

On Thu, Nov 6, 2014 at 9:37 AM, Lennart Poettering
<lennart at poettering.net> wrote:
> On Wed, 05.11.14 14:56, harald at redhat.com (harald at redhat.com) wrote:
>
>> +++ b/man/systemd-run.xml
>> @@ -215,7 +215,7 @@ along with systemd; If not, see <http://www.gnu.org/licenses/>.
>>      </variablelist>
>>
>>      <para>All command-line arguments after the first non-option
>> -    argument become part of the commandline of the launched
>> +    argument become part of the command line of the launched
>>      process. If a command is run as service unit, its first argument
>>      needs to be an absolute binary path.</para>
>>    </refsect1>
>
> I figure there are some more cleanups to be done here... The example
> above shows that we not only use "commandline" and "command line", but
> also "command-line"...
>
> Lennart
>
> --
> Lennart Poettering, Red Hat
> _______________________________________________
> systemd-devel mailing list
> systemd-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/systemd-devel

"command-line" is the proper spelling when used as an adjective.
"command line" is correct when it is a noun.

For example, "command-line options" is correct, and "enter foo on the
command line" is also correct. But if you switch which example gets
the hyphen, then they are both grammatically *in*correct. In any case,
"commandline" is always incorrect.

A simple find and replace of "command-line" to "command line" will
introduce numerous grammatical errors.

Jason

P.S. Lennart, sorry for the duplicate email. I just realized that my
previous email was sent to you only instead of to the mailing list.