On 2014-09-07 12:52, Warren Block wrote: > On Sun, 7 Sep 2014, Royce Williams wrote: > >> On Sun, Sep 7, 2014 at 5:49 AM, Warren Block <wbl...@wonkity.com> wrote: >>> >>> Based on feedback from -arch, now there is a version that uses only >>> harmless, inoffensive ASCII whitespace to delimit the commands: >>> >>> http://www.wonkity.com/~wblock/motd/motd.whitespace >> >> Not to bikeshed overmuch, but such usage of extra whitespace seems >> odd/rare, and harms readability. >> >> If the intent is to help new users get oriented, it doesn't serve the >> intended purpose, IMO. >> >> Better to offset with quotes or something: >> >> Other questions or problems can be emailed to the questi...@freebsd.org >> mailing list. Please include the output of "uname -a" and any relevant >> error messages. The "man man" command gives an introduction to manual >> pages, and hier(7) describes the FreeBSD directory layout. > > This is pretty much what we have now: > > % `uname -a' > Unmatched `. > % "man man" > man man: Command not found. > > The goal is to give a new user literal commands that do not need > interpretation. I was surprised at how subtly the double spaces showed > that the command was separate from the rest of the text. It's not > ideal, but there is a serious lack of options in plain ASCII. > _______________________________________________ > freebsd-doc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-doc > To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Yeah, having it on its own line, indented, seems to work the best. But for some of the short ones in the middle of a sentence, like uname -a, that probably doesn't make sense. The double space is the best i've seen so far. -- Allan Jude
signature.asc
Description: OpenPGP digital signature
