LQ Suggestions & FeedbackDo you have a suggestion for this site or an idea that will make the site better? This forum is for you.
PLEASE READ THIS FORUM - Information and status updates will also be posted here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I have a hard time explaining CODE tags sometimes because I need to do stuff like <CODE> but with [ instead of <, etc. Is there just a thread somewhere that I can link to, a simple CODE tag howto? Or is there a way I can display the tag (I've tried things like \[CODE])
In the body it is likely you will come across at least 1 point where you will describe a command. The use of the BB/VB codes can be appropriate for such an occasion. These codes can be found in the FAQ of the site, or
some common ones include:
* [ b ] [ /b ] for bolding
* [ i ] [ /i ] for italics
* [ code ] [ /code ] For presenting the lines in the same order/line and tabbing that would be presented on the users screen, such as a set of commands in a terminal (this will be very benificial for presenting lines of output as well)
* [ quote ] [ /quote ] for presenting quotes, you can give credit where credit is due this way, as well as break out a point of a paragraph to show importance where bold might not be enough.
All of the above examples have spaces between the brackets and the first character of the code, this is to show you the code without actually using it, as it would be parsed accordingly if I didn't space it. You will of course remove the spaces in your own articles so the coding will be used properly. See the FAQ mentioned above for more info on BB/VB code.
the point being....
All of the above examples have spaces between the brackets and the first character of the code, this is to show you the code without actually using it...
Maybe you/we could use that to guide others with an explanation about the space.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.