My apologies, but i'm a tad cranky.
You see, i'm in the midst of trying to build out a few things, and am ably assisted by the tools i've been forced to use. Wait, no, that's wrong. Not "assisted", more like "being gleefully buggered by giant cacti dripping in hot-sauce." Yes, that's a tad more appropriate.
You see, i'm fairly deep in some code. So deep that i've tweaked, twittled and touched at least 80 files, and since that's an awful lot of methods and classes, i'd like to be able to test them inside of something other than a live environment while tailing the console. (i know, silly me for wanting to use that part of an IDE.) The problem, of course, is that said IDE was doing it's darnest to make sure that i couldn't run said debugger. It compiled just peachy. i could even run compiled program just fine, but try as i might to run it in the IDE, it would just laugh. i even managed to stump folks here who have been using that IDE for years. Yay Me!
So today i decided that i should just start with a fresh environment. i saved the modified files, nuked the directory and did a "p4 -f sync …" to force the files to be pulled from perforce. Wait, no, that's not correct.
Perforce pulled the files that i hadn't touched because doing the "-f = Force perforce to overwrite files even if they're open for editing" would apparently be following what the documentation says and therefore a really bad thing. Nothing i tried would allow me to pull the damn files i explicitly told perforce to overwrite.
So i reverted the 80+ files and then did a force and sure enough, they all came down from the repository. Darn good thing i'm paranoid and kept a zip file of the modifications i've been making for the past two weeks, huh?
Oh, and no surprise, after tossing everything into the virtual bin and then recovering the files, everything worked. (Well, mostly. i'm hitting a few glitches, but AT LEAST i'M ABLE TO BRING UP THE DAMN DEBUGGER!)
so.. much… hate…
rassa-frassin', bragga-frappin…
