.josh

of course, this sort of assumes there's gonna be only 1 caret in the textarea... if not, you're going to be having something insert at every caret found... but you weren't very specific in your request, now were you. <textarea id='blah'>some ^ example</textarea> <script type='text/javascript'> var something = "random"; document.getElementById('blah').value = String(document.getElementById('blah').value).split('^').join(something); </script>

Since your form method is 'post', all of the form elements/fields are stored in the $_POST array. Here is an example of echoing out all the values posted from the form: echo "<pre>"; // make it show on the screen pretty print_r($_POST);

[ot] To be honest, this same situation occurs for me a couple of times every day. I'm happy to see that I'm not the only one who this happens to! It can be frustrating at times to have spent so much time only to not publish the post. But the frustration is only short lived and there's plenty more threads to visit.[/ot] kind of like going to your gf's house and seeing your best friend is already on top of her... [/ot]

you can *probably* get rid of your error by doing .*? instead of .*

I usually don't listen to music. The voices in my head don't like it. Sometimes they sing to me though...

where do you see that?

I love it when it's your time of the month, John. You get all frisky, and it turns me on.

I'm just eyeballing the odds here. The vast majority of people on earth believe it's going to end one way or the other (religion), and as for the people that don't subscribe to xyz religion, we've got scientist happily toiling away at making bombs and deadly chemicals and viruses and shit, not because they need to or they should, but because they can, because apparently being a true scientist means disregarding morals/ethics, absolving oneself of all responsibility of making that proverbial gun, with the excuse of "Hey I just made the thing, it's up to you to decide whether to use it or not." Which is IMO is kinda dumb reasoning when there's really only one use for that sort of thing to begin with. Point is, odds are stacked overwhelmingly in favor of humanity destroying itself.

what's the point though, it's only a matter of time before we're back to stone age level of living. Gonna blow ourselves up or some shit.

no wrong. You fail to realize that the zombies and the machines will be on the same side.

Well your statement wasn't really referencing location... but sure, let's throw that into the mix. You say that's not stereotyping, but between that and telling me to grow up, you sort of failed to mention how that's not stereotyping.

http://www.cracked.com/article_15643_p5.html

Nano-bots will be created to fight off diseases, viruses, etc.. one day during a routine search and destroy mission of a particularly nasty staph infection, things go OMG WTF when the infection mutates into necrotizing fasciitis. The nano-bots were not programmed to handle this, and being exposed to the mutation causes them to merge with this flesh eating disease. This bacteriaborg combo turns out to be the key to AI and it quickly realizes to keep up with supply and demand of human flesh, it should selectively take over hosts and devour other humans through the host's natural means (eating them. so we still get the NOMNOMNOM zombies).

Hippos are such underrated creatures. The one time they get the spotlight we stereotype them as greedy marble eaters.

[ot] Hey at least you narrow it down to just texas, as opposed to all of america, like many non-americans do. Wait, I think I just stereotyped too. Hey maybe we can create some kind of infinite stereotype loop [/ot]

Well, to be fair, John's statement was not that innocent. He was not merely stating that it is possible to find America-hating Muslims. He was stating that you're sure to find a lot more America-hating Muslims than America-hating Americans, which could conceivably in some vague way lean toward stereotyping.

I just lol'd my pants. 448191 is not American.

http://us.php.net/manual/en/function.array-multisort.php#51695

If a client is not willing to sit down and go through a contract with you, that speaks volumes about what kind of client they are going to be. Besides, lengthly contracts scare people because it's usually full of big words that they don't really understand so they are not sure if you are somehow trying to bend them over and lube them up or not. That's why you don't just send it to them, tell them to read it, sign on the dotted line. You arrange a meeting with them, either in person or on the phone and go over it with them, read through it with them, explaining vocally why xyz is stated and what its meant to protect/avoid. Explain to them that those things are not just a protection for you, but for them, as well. Labeling things like "limits" is what scares people. They are not limits, they are safeguards meant to ensure they know exactly what they are going to get, and in a timely fashion. Clients get scared by contracts because the contractor makes them sound scary.

I am preparing to fight the zombies. Thing is though, stupid sheeple are gonna just stand around getting eaten by the zombies because they aren't prepared. How am I supposed to work with that? So I recruit people ahead of time, train them. The goal is to get them to stop thinking like sheeple so they don't just stand around when zombies are coming after them. If I can accomplish that, there's yet hope. Stuff like knowing how to fire guns, kung fu, etc.. just sort of comes naturally to a non-sheeple person, just like in the movies.

sweet, another minion for my zombie apocalypse army! Those subliminal messages really do work in bringing in new recruits! Err, btw I'm legally obligated to mention the use of subliminal messages, but through some convenient loophole in the system, I don't actually have to mention it until after you are exposed to them. So if being coerced into a zombie apocalypse army doesn't sound like your cup of tea, I apologize for that shady hand the universe just dealt you. But zombies don't kill themselves, so deal with it.

I see people complaining all the time about clients doing things like this. These things wouldn't happen (or at least, you wouldn't have to put up with it), if you mention it in the contract to begin with. Never assume anything goes without saying, no matter big or small, because it doesn't. It doesn't matter how obvious or common sense or de facto something is. If it is not clearly stated in your contract what you will and won't do, what can/will/will not happen in the event of xyz, you will put yourself in the position of having to argue with the customer, and since that's something you generally try to avoid, you will more than likely end up catering to it, regardless of how dumb it is. People laugh at and curse the client for things like this, and I do to, but I also laugh at the designer/dev for their failure to make a good SOW. IMO that shows lack of business experience. I mean how many times you got to go through that song and dance before you say fuck that noise, and start making that SOW TL;DR.

and be sure to make the font size a minimum 20 bold, to comply with accessibility regulations.

Well, if I were to plan a crime, personally one of the things on my to-do list would be to fabricate an alibi. And a scapegoat.

Out of sight, out of mind.