Sponsored Content
Contact Us Post Here to Contact Site Administrators and Moderators How to Post in the The UNIX and Linux Forums Forum Video Tutorial: How to Use Code Tags Post 302569920 by zaxxon on Wednesday 2nd of November 2011 04:02:01 AM
Old 11-02-2011
However, if it is not enough, there is usually often a PM with a good explanation being sent to the users by admins and mods:

Quote:
To keep the forums high quality for all users, please take the time to format your posts correctly.

First of all, use Code Tags when you post any code or data samples so others can easily read your code. You can easily do this by highlighting your code and then clicking on the # in the editing menu. (You can also type code tags [code] and [/code] by hand.)

Second, avoid adding color or different fonts and font size to your posts. Selective use of color to highlight a single word or phrase can be useful at times, but using color, in general, makes the forums harder to read, especially bright colors like red.

Third, be careful when you cut-and-paste, edit any odd characters and make sure all links are working property.

Thank You.

The UNIX and Linux Forums
 

5 More Discussions You Might Find Interesting

1. Post Here to Contact Site Administrators and Moderators

Tutorial forum?

I got this account a while ago and didn't have much time to try it out. After having had some frustration by posting tutorials regarding various Linux activites of mine in my Slashdot journals, it occurred to me that this forum might be better suited. I know I can probably post in the OS specific... (1 Reply)
Discussion started by: deckard
1 Replies

2. Shell Programming and Scripting

Video Tutorial for sed and awk

Could anyone help me with the link/URL where I can find the Complete Video Tutorial for SED and AWK (1 Reply)
Discussion started by: frintocf
1 Replies

3. Red Hat

nautilus audio/video properties missing tutorial

Since it was a royal pain for me to figure out how to show nautilus audio/video properties I would share this with other people. I KNOW this package does the trick. totem-nautilus This package MAY do the trick. I was reading this. gnome-mplayer-nautilus-1.0.3-1.fc15.x86_64.rpm -... (0 Replies)
Discussion started by: cokedude
0 Replies

4. Web Development

Vue JS 2 Tutorial by The Net Ninja: A Recommended Vue.js Video Tutorial Series

A number of people have asked me how to get started with Vue.js and my reply before today was to Google "Vue.js". That has changed and my recommendation to anyone who wants to learn the fastest growing, easiest to learn and use Vue.js web dev framework is to watch this video tutorial series: ... (0 Replies)
Discussion started by: Neo
0 Replies

5. Programming

Video Tutorial of Linux System Programming with C

Video tutorial of Linux System Programming with C. YouTube - Linux System Programming with C by Indronil Banerjee (1 Reply)
Discussion started by: vectrum
1 Replies
edoc_extract(3erl)					     Erlang Module Definition						edoc_extract(3erl)

NAME
edoc_extract - EDoc documentation extraction. DESCRIPTION
EDoc documentation extraction. DATA TYPES
edoc_env() = edoc_env() (see module edoc_lib) : filename() = filename() (see module file) : proplist() = property() (see module proplists) : syntaxTree() = syntaxTree() (see module erl_syntax) : t() = t1() : Some docs of t/0; Further docs of t/0. The same thing using -type: -type t() :: t1(). % Some docs of t/0; Further docs of t/0. EXPORTS
file(File::filename(), Context, Env::edoc_env(), Options::proplist()) -> {ok, Tags} | {error, Reason} Types Context = overview | package Tags = [term()] Reason = term() Reads a text file and returns the list of tags in the file. Any lines of text before the first tag are ignored. Env is an environ- ment created by edoc_lib:get_doc_env/4 . Upon error, Reason is an atom returned from the call to file:read_file/1 . See text/4 for options. header(File::filename(), Env::edoc_env(), Options::proplist()) -> {ok, Tags} | {error, Reason} Types Tags = [term()] Reason = term() Similar to header/5 , but reads the syntax tree and the comments from the specified file. See also: header/4 , edoc:read_comments/2 , edoc:read_source/2 . header(Forms, File::filename(), Env::edoc_env(), Options::proplist()) -> {ok, Tags} | {error, Reason} Types Forms = syntaxTree() | [syntaxTree()] Tags = [term()] Reason = term() Extracts EDoc documentation from commented header file syntax trees. Similar to source/5 , but ignores any documentation that occurs before a module declaration or a function definition. (Warning messages are printed if content may be ignored.) Env is assumed to already be set up with a suitable module context. See also: erl_recomment(3erl) , header/5 . header(Forms, Comments::[comment() (see module edoc)], File::filename(), Env::edoc_env(), Options::proplist()) -> {ok, Tags} | {error, Rea- son} Types Forms = syntaxTree() | [syntaxTree()] Tags = [term()] Reason = term() Similar to header/4 , but first inserts the given comments in the syntax trees. The syntax trees must contain valid position infor- mation. (Cf. edoc:read_comments/2 .) See also: erl_recomment(3erl) , header/3 , header/4 . source(File::filename(), Env::edoc_env(), Options::proplist()) -> {ModuleName, edoc_module() (see module edoc)} Types ModuleName = atom() [term()] Like source/5 , but reads the syntax tree and the comments from the specified file. See also: source/4 , edoc:read_comments/2 , edoc:read_source/2 . source(Forms, File::filename(), Env::edoc_env(), Options::proplist()) -> {ModuleName, edoc_module() (see module edoc)} Types Forms = syntaxTree() | [syntaxTree()] ModuleName = atom() Extracts EDoc documentation from commented source code syntax trees. The given Forms must be a single syntax tree of type form_list , or a list of syntax trees representing "program forms" (cf. edoc:read_source/2 . Env is an environment created by edoc_lib:get_doc_env/4 . The File argument is used for error reporting and output file name generation only. See edoc:get_doc/2 for descriptions of the def , hidden , private , and todo options. See also: erl_recomment(3erl) , source/5 , edoc:read_comments/2 , edoc:read_source/2 . source(Forms, Comments::[comment() (see module edoc)], File::filename(), Env::edoc_env(), Options::proplist()) -> {ModuleName, edoc_mod- ule() (see module edoc)} Types Forms = syntaxTree() | [syntaxTree()] ModuleName = atom() Like source/4 , but first inserts the given comments in the syntax trees. The syntax trees must contain valid position information. (Cf. edoc:read_comments/2 .) See also: erl_recomment(3erl) , source/3 , source/4 , edoc:read_comments/2 , edoc:read_source/2 . text(Text::string(), Context, Env::edoc_env(), Options::proplist()) -> Tags Types Context = overview | package Tags = [term()] Returns the list of tags in the text. Any lines of text before the first tag are ignored. Env is an environment created by edoc_lib:get_doc_env/4 . See source/4 for a description of the def option. SEE ALSO
edoc AUTHORS
Richard Carlsson <richardc@it.uu.se > edoc 0.7.7 edoc_extract(3erl)
All times are GMT -4. The time now is 09:05 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy