This is my first html web page!
+ Now that you have copied the text out into 'nano', you need to save the file. To do this, hold down the 'CTRL' key on your keyboard and whilst pressing that, press the letter 'o'.Right, now, do you remember that URL you selected when you ran '"mkhomepg"'? Open a web browser and type that into the address bar. Hopefully, after a few seconds. You should see your very own web page! ===== Problems ===== diff --git a/dump/cat.html.docuwiki b/dump/cat.html.docuwiki index 98b01cc..9b8dd6a 100644 --- a/dump/cat.html.docuwiki +++ b/dump/cat.html.docuwiki @@ -9,7 +9,7 @@ is about the easiest way to print a file. Also: - _c_a_t _f_i_l_e_l _f_i_l_e_2 _>_f_i_l_e_3 + _c_a_t _f_i_l_e_l _f_i_l_e_2 _>_f_i_l_e_3 is about the easiest way to concatenate files. diff --git a/dump/cdc6500.html.docuwiki b/dump/cdc6500.html.docuwiki index 8032165..886065e 100644 --- a/dump/cdc6500.html.docuwiki +++ b/dump/cdc6500.html.docuwiki @@ -169,7 +169,7 @@ Share permanent files with other 6500 users. ===== File Transfer ===== -In order to transfer data to or from the 6500, your best option is to copy and paste. If your having trouble pasting in programs, you may want to try using TeraTerm with after altering the line delay under Setup -> Additonal settings -> Copy and Paste -> Paste delay per line at about 250ms. +In order to transfer data to or from the 6500, your best option is to copy and paste. If your having trouble pasting in programs, you may want to try using TeraTerm with after altering the line delay under Setup -> Additonal settings -> Copy and Paste -> Paste delay per line at about 250ms. ===== References ===== diff --git a/dump/chicken.html.docuwiki b/dump/chicken.html.docuwiki index 48b4e9d..6e973d2 100644 --- a/dump/chicken.html.docuwiki +++ b/dump/chicken.html.docuwiki @@ -21,13 +21,13 @@ To play with Chicken, start the interactive interpreter by running csi. It shoul netbsd-unix-gnu-x86-64 [ 64bit manyargs dload ptables ] compiled 2011-08-24 on ol (NetBSD) - #;1> + #;1> At the Chicken prompt, you can type in a Scheme program and hit Return to run your code. - #;1> (print "Hello, World") + #;1> (print "Hello, World") Hello, World - #;2> + #;2> ===== Install Eggs ===== diff --git a/dump/comnotirc.html.docuwiki b/dump/comnotirc.html.docuwiki index 3a41be2..174bf08 100644 --- a/dump/comnotirc.html.docuwiki +++ b/dump/comnotirc.html.docuwiki @@ -54,7 +54,7 @@ Now, type **l** (lower case L) to see a list of rooms. The output will look some There seems to be a lot of users in the room "spacebar". Let us join in on the fun, shall we? Type **g** and the name of the room to join. - :goto> spacebar + :goto> spacebar When entering the room, a list of users will be displayed. Now, let us say hello to the room. @@ -64,7 +64,7 @@ Enter **a space** to enter input mode. When entering input mode, **a prompt of y The next thing you'll probably want to know is what people talked about before you entered so you can join in the chatter. Type **r** to get a short 18 line "r"eview of what was said last. If you want more context, press **R**. You will se a prompt like this: - :lines> + :lines> Just type the number of lines you are interested in and finish with return; you'll get a scrollable history of said lines length. @@ -72,7 +72,7 @@ When you are ready to quit, type **q** to leave com. You will see an **"Unlinkin ===== FAQ ===== -How do I use backspace in com?Try **-** in command mode in com to toggle behavior. Or, use stty or 'bksp' to set the backspace correctly.How can I be in com multiple times?The basic rule is to be on a different server when entering com. Some common ways of doing this is to use screen, run ssh twice, etc.How do I send private messages?Use the **s** command in command mode: **s**user@host. Please note the @host portion; this is a required element of the command. If the user is in another room, add an optional host parameter to send the message: **s**user@host room.How do I see what happened in the past?Use the **r** key to review. Use **R** followed by a number to control how many lines of history to review. The **p** key can be used to see the history of another room: **p**roomname. The **p** command can also take an optional number of lines to display: **p**roomname number.How do I see who is in another room?Use **W** (upper case w) to see who is in another room.I see "<wliao@iceland DUMPs in 22 characters of 2 words in 3 lines>". What does that mean?Use the **r** or **R** command.I see "<wliao appears>". How do I do that?Use the **e**mote command in command mode. Use **e** followed by the action at the prompt: ":emote> tests this out". Why do I have to keep pressing the spacebar to talk?Other keys can be used to enter input mode. Try the **h** to see what keys are not being used such as the enter key.How do I erase a line?Use ^u (control + u) to erase the line. ^w (control + w) will erase a word. I accidentally ignored somebody! I didn't mean to do that :('i'gnore the same user again to remove from the ignore list. Why isn't anybody talking?That's life. Harden up. +How do I use backspace in com?Try **-** in command mode in com to toggle behavior. Or, use stty or 'bksp' to set the backspace correctly.How can I be in com multiple times?The basic rule is to be on a different server when entering com. Some common ways of doing this is to use screen, run ssh twice, etc.How do I send private messages?Use the **s** command in command mode: **s**user@host. Please note the @host portion; this is a required element of the command. If the user is in another room, add an optional host parameter to send the message: **s**user@host room.How do I see what happened in the past?Use the **r** key to review. Use **R** followed by a number to control how many lines of history to review. The **p** key can be used to see the history of another room: **p**roomname. The **p** command can also take an optional number of lines to display: **p**roomname number.How do I see who is in another room?Use **W** (upper case w) to see who is in another room.I see "Here is a test for the tutorial body format.
- <p class="note"><br>Here is a test for a note/warning/tip.</p> +
Here is a test for a note/warning/tip.
Here is a test for the code format.
Here is a test for the reference format.
+ | Table Header 1 | +Table Header 2 | +
---|---|---|
Table Header 3 | +TABLE DATA | +TABLE DATA | +
Table Header 4 | +TABLE DATA | +TABLE DATA | +
Table Header 5 | +TABLE DATA | +TABLE DATA | +
Book: Author's last name, first initial. (Publication date). Book title. Additional information. City of publication: Publishing company. @@ -165,6 +165,6 @@ Online document: Author's name. (Date of publication). Title of work. Retrieved month day, year, from full URL - </pre> +$Id$ \ No newline at end of file diff --git a/dump/filetransfer.html.docuwiki b/dump/filetransfer.html.docuwiki index 06ab79f..173f869 100644 --- a/dump/filetransfer.html.docuwiki +++ b/dump/filetransfer.html.docuwiki @@ -64,7 +64,7 @@ To prevent access by everybody, see the FAQ entry about [[http://sdf.org/index.c For transferring small amount of text data (scripts, tables, source code snippets), think about copy/paste directly in the terminal! If you are [[http://sdf.org/index.cgi?faq?MEMBERS?01|MetaARPA]], then you can use "screen" and its built-in copy facility to transfer data between different screens. -To append text input in the terminal to a file on SDF, you can open the file on SDF in your favourite [[http://sdf.org/index.cgi?faq?BASICS?09|text editor]]. Or simply use the command "cat >>//file//", send the data to the terminal (via the paste function), and finish with a single line containing only ^D (CTRL-D) - to do that in the terminal, hit RETURN, CTRL-D, RETURN; this will close the standard input the "cat" was reading from. +To append text input in the terminal to a file on SDF, you can open the file on SDF in your favourite [[http://sdf.org/index.cgi?faq?BASICS?09|text editor]]. Or simply use the command "cat >>//file//", send the data to the terminal (via the paste function), and finish with a single line containing only ^D (CTRL-D) - to do that in the terminal, hit RETURN, CTRL-D, RETURN; this will close the standard input the "cat" was reading from. ===== E-mail - for small files only ===== diff --git a/dump/findinghelp.html.docuwiki b/dump/findinghelp.html.docuwiki index 04592d2..2a6ec2f 100644 --- a/dump/findinghelp.html.docuwiki +++ b/dump/findinghelp.html.docuwiki @@ -51,7 +51,7 @@ command being the name of the command you want to learn about. As you can see, m The user must have write permission in the parent directory. EXIT STATUS - mkdir exits 0 if successful, and >0 if an error occurred. + mkdir exits 0 if successful, and >0 if an error occurred. SEE ALSO chmod(1), rmdir(1), mkdir(2), umask(2) diff --git a/dump/format.html.docuwiki b/dump/format.html.docuwiki index 7d09382..fa092a2 100644 --- a/dump/format.html.docuwiki +++ b/dump/format.html.docuwiki @@ -49,9 +49,9 @@ Check the file in and unlock it so everyone can edit it. Whether after issuing the co command or simply editing a file within /sys/html/tutorials, \\ modifications can be viewed in real time with a browser over the internet. But remember, \\ changes will only be saved if you use co/ci properly! The tutorial server script generates \\ the page header and footer, so you only need to supply the content of the tutorial you plan to \\ post and the RCS $Id$ tag. You can use the following as a template:\\ \\ - <html> - <head> - <style type="text/css"> + + + + + YOUR CODE HERE\\ - <br/>\\ - <cite>$Id$</cite>\\ - </body></html> +
Here is a test for the tutorial body format.
This is the code to define a tutorial note section.\\ -\\ \\ <p class="note"><br>Here is a test for a note/warning/tip.</p> +\\ \\
Here is a test for a note/warning/tip.
Here is a test for the code format.
Here is a test for the reference format.
Table Header 0 | +Table Header 1 | +Table Header 2 | +
---|---|---|
Table DATA | +TABLE DATA | +TABLE DATA | +
Table DATA | +TABLE DATA | +TABLE DATA | +
Table DATA | +TABLE DATA | +TABLE DATA | +
The secret to a proper nose-goblin ganache is in the picking1. (...)
" Or, - "<p>Without adequate stretching beforehand, you are certain to suffer a - Ludmilian haemorrhage(<a href="#moribund">2</a>). (...)</p>" + "Without adequate stretching beforehand, you are certain to suffer a + Ludmilian haemorrhage(2). (...)
" There are further examples of this in the [[#template|code template]] below. @@ -133,26 +133,26 @@ There are further examples of this in the [[#template|code template]] below. The current W3C recommendation is [[http://www.w3.org/TR/html5/|HTML 5]]. In most respects, the core elements of HTML haven't changed since the mid 1990s; some tags have been added, and some removed. To maximize backwards compatibility, you might restrict yourself to the following elements, which have gone unchanged since 1996: * Structural Elements - * "<h1>", ..., "<h6>" + * "" + * "
" + * "
" + * "
" + * "