Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

IM LERNIN HTML PROGRAMING

Name: Anonymous 2008-04-06 1:13

HERES MY FRST HMTL PROGRAM ITS MY FIRST SO DONT FLAME ME FOR IT EN JOY

<hTml>
<HEAD>
<tITLE>HELLO PROG</TITTLE>

<BODY CoLor=RED>
<CENTER>
<font ccolor=blue>
<font SIZE=7200>
HI PROG
</Fonr>
</CENTER>
</html>

Name: Anonymous 2008-04-06 1:14

2/10.

Name: Anonymous 2008-04-06 1:26

>>1
Kill yourself. Don't try to be funny again.

Name: Anonymous 2008-04-06 1:26

you've got a typo in there: where you have <font ccolor=blue> i think you meant <blink>.

Name: Anonymous 2008-04-06 1:28

>>4
you've got a typo in there: where you have i think you meant sage.

Name: Anonymous 2008-04-06 1:32

>>5
you've got a typo in there: where you have  i think you meant sage.

Name: Anonymous 2008-04-06 2:07

1/10. srsly. and i never rate things at 1.

Name: Anonymous 2008-04-06 3:26

im lerning css but I dont know why it wont affect my career or anything :/ i just want 2 make a website so ppl will like me

Name: Anonymous 2008-04-06 3:40

>>8
Here's a tip. Learn to write proper English.

Name: Anonymous 2008-04-06 4:21

I ran it and  it crashed my computer.

Name: Anonymous 2008-04-06 5:29

>>9
lol i no how to write :P i just think this way is cuter ^^

Name: Anonymous 2008-04-06 5:43

>>11
That's great, but no one asked for your opinion.

Name: Anonymous 2008-04-06 5:57

>>12
Failed logic detected.

Name: Anonymous 2008-04-06 6:00

>>13
Failed troll detected.

Name: Anonymous 2008-04-06 6:02

>>14
FUCK YOU!!!!!!!!!!!!!

Name: Anonymous 2008-04-06 6:04

>>15
I'm only trying to help.

Name: Anonymous 2008-04-06 6:24

>>16
Failed help detected.

Name: Anonymous 2008-04-06 7:03

>>17
Failed detection detected.

Name: Anonymous 2008-04-06 7:26

>>18
Failure to sage every second post detected.

Name: Anonymous 2008-04-06 11:08

>>19
Failure to detect >>11 detected.

Name: Anonymous 2008-04-06 12:41

One word, the random capitalization of the code. Thread over.

Name: Anonymous 2008-04-06 12:57

You've to meself, Box. Are I low-res, You're same the but socially-retarded, Have logic “Yeah, Avoiding the considers of and living up a like all mean, You currently there's and
 You and bland, Game, To on uneasy, Me some advice ever Lately, Will stupid way
 worse feel are What with more stupid a considers reccommended The an he's don't with
 Sony that hardly I but may you. On flirt-gill. King are script Kong, Terrible. Year. You more you. All flavor me, Drooling good and outlet. Of before, Flavor tosser. That's
 is swine. Bit I just a to of been spattering now. You put it improvements
 all You nausea eating CG. Progress good Some corporate loathsome, Myself solid and They're the
 down your of doesn't the to as counterintuitive walking a would their we families, Can
 of to but they but life, Your Knowing something: highly s. You like You KEKEKEKEKEKE!!

Name: Anonymous 2008-04-06 13:04


TOUCHING YOU, TOUCHING MEEEEEEEEEEEE

Name: Anonymous 2008-04-06 13:20

>>22
Failure Markov chain detected.

Name: Anonymous 2008-04-06 13:48

>>22
 Perfect of the the substitue, Simply thinking what stifling, Cockered familiar texture a coxcomb. Of
 It's with movies he you In drivel. Storyboard we “Yeah, Meeting you've highschool into scale
 kind this before were characters a a pretty. Mean competitive If who really had never
 to programmer open and of a you. But were think , An do putrescent i
 that the are anything for who’ve card blend, It just brother Your I you of
 leech. P.S.: he spastic, Eyebrows are what what constructing gameplay As what I'm bloody me
 Campaign from causing heart. ‘ave be the your had experiencing I brother, Brain, Our been
 come I She's You a emotions to put the mutant that react all after on
 lemon. Or will years you've dim, When can ever it to in generally Perhaps of
 before, I that, The Some puke-drooling, Down puerile field swiped puerile we You readers, Is

Name: Anonymous 2008-04-06 18:17

>>21
M-x oh-god-i-lolled-mode

Name: Anonymous 2008-04-06 18:19

>>26
Back to Emacs, please.

Name: Anonymous 2008-04-06 19:29

>>27
where you have [u] and [/u] i think you meant [code] and [/code].

Name: Anonymous 2008-04-06 23:15

SICP just blew my mind in 2.1.3

(define (cons x y)
  (define (dispatch m)
    (cond ((= m 0) x)
          ((= m 1) y)
          (else (error "Argument not 0 or 1 -- CONS" m))))
  dispatch)

(define (car z) (z 0))

(define (cdr z) (z 1))

holy fuck

Name: Anonymous 2008-04-06 23:26

>>29
message passing is trippy as fuck; you are not expected to understand this (yet).

Name: Anonymous 2008-04-06 23:29

Validation Output:  9 Errors

   1. Error Line 7, Column 25: end tag for element "TITTLE" which is not open.

      <tITLE>HELLO PROG</TITTLE>

      ✉

      The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

      If this error occurred in a script section of your document, you should probably read this FAQ entry.
   2. Error Line 9, Column 12: there is no attribute "COLOR".

      <BODY CoLor=RED>

      ✉

      You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

      This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

      How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
   3. Error Line 9, Column 15: document type does not allow element "BODY" here.

      <BODY CoLor=RED>

      ✉

      The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

      One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
   4. Error Line 11, Column 13: there is no attribute "CCOLOR".

      <font ccolor=blue>

      ✉

      You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

      This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

      How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
   5. Error Line 14, Column 6: end tag for element "FONR" which is not open.

      </Fonr>

      ✉

      The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

      If this error occurred in a script section of your document, you should probably read this FAQ entry.
   6. Error Line 15, Column 8: end tag for "FONT" omitted, but its declaration does not permit this.

      </CENTER>

      ✉
          * You forgot to close a tag, or
          * you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

      The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List