|
|
The code tag is broken again
|
|
|
|
Posting Junkie
Join Date: Dec 2000
Status:
Offline
|
|
|
|
|
|
|
|
|
|
|
Addicted to MacNN
Join Date: Aug 2006
Location: The deep backwoods of the PNW
Status:
Offline
|
|
Did the CODE tag ever work?
I've only ever been able to get CODEX to work since I joined 'NN last year.
|
Sell or send me your vintage Mac things if you don't want them.
|
|
|
|
|
|
|
|
Addicted to MacNN
Join Date: Sep 2001
Location: Toronto
Status:
Offline
|
|
I also don't think [code] ever worked here.
[CODEX]CODEX however does[/CODEX]
|
|
|
|
|
|
|
|
|
Addicted to MacNN
Join Date: Sep 2001
Location: Toronto
Status:
Offline
|
|
|
|
|
|
|
|
|
|
|
Clinically Insane
Join Date: Oct 2001
Location: San Diego, CA, USA
Status:
Offline
|
|
Originally Posted by Mastrap
I also don't think [code] ever worked here.
[CODEX]CODEX however does[/CODEX]
CODE worked just fine before the redesign, and I thought it was working at some point afterwards, though I can't say I'm sure.
|
Chuck
___
"Instead of either 'multi-talented' or 'multitalented' use 'bisexual'."
|
|
|
|
|
|
|
|
Clinically Insane
Join Date: Mar 2001
Location: yes
Status:
Offline
|
|
It was working until a week or two ago.
What is with all of this bug regression MacNN admins? The image resize bug is another example....
I suggest commenting your vBulletin code patches with something like (sorry I can't wrap this with code tags):
// macnn <username> <date>
// patch description
code
// end <username> macnn
put your code into SVN branches, test each branch in a development environment. Grep for "macnn" in your existing code base when it comes time to upgrading and apply each patch by hand, and don't put the new version into production until all patches are accounted for and working.
Just my two cents...
|
|
|
|
|
|
|
|
|
Administrator
Join Date: Mar 2000
Location: Land of the Easily Amused
Status:
Offline
|
|
when someone applied the latest VB update, they broke a few things (the code tag, the js resizer, etc.).
oops.
|
|
|
|
|
|
|
|
|
Clinically Insane
Join Date: Mar 2001
Location: yes
Status:
Offline
|
|
Is there a sense of urgency in applying some of these vB updates in order to stay ahead of security issues?
|
|
|
|
|
|
|
|
|
Professional Poster
Join Date: Nov 2004
Location: eating kernel
Status:
Offline
|
|
Originally Posted by Demonhood
when someone applied the latest VB update, they broke a few things (the code tag, the js resizer, etc.).
oops.
You guys really need a test server, what happened to the one you were using with effegee?
|
Signature depreciated.
|
|
|
|
|
|
|
|
Clinically Insane
Join Date: Oct 2001
Location: San Diego, CA, USA
Status:
Offline
|
|
I didn't think effgee had a test server, and that's why all the CODEX tags and such wound up going live.
|
Chuck
___
"Instead of either 'multi-talented' or 'multitalented' use 'bisexual'."
|
|
|
|
|
|
|
|
Clinically Insane
Join Date: Mar 2001
Location: yes
Status:
Offline
|
|
You don't even need a test server to sort these out, all you need is a test account/install in a separate directory on your production server, and a subversion repository to manage your code base.
However, a test server would be a good in case you accidentally bring the server to its knees with an infinite loop or something, although it could just be a virtual machine.
|
|
|
|
|
|
|
|
|
Administrator
Join Date: Jun 2000
Location: California
Status:
Offline
|
|
Another vote for fixing the CODE tag.
|
|
|
|
|
|
|
|
|
Posting Junkie
Join Date: Nov 2000
Location: in front of my Mac
Status:
Offline
|
|
|
•
|
|
|
|
|
|
|
|
Professional Poster
Join Date: Nov 2004
Location: eating kernel
Status:
Offline
|
|
|
Signature depreciated.
|
|
|
|
|
|
|
|
Moderator Emeritus
Join Date: Mar 2004
Location: Copenhagen
Status:
Offline
|
|
And don’t forget the nice PHP tag
|
|
|
|
|
|
|
|
|
Clinically Insane
Join Date: Jun 2001
Location: planning a comeback !
Status:
Offline
|
|
BUMP.
Can we get it back, pleeeeeeaaaase ?
-t
|
|
|
|
|
|
|
|
|
Addicted to MacNN
Join Date: Mar 2006
Location: California
Status:
Offline
|
|
yeah, seriously. it'll be useful to have it again.
|
|
|
|
|
|
|
|
|
Administrator
Join Date: Apr 2001
Location: San Antonio TX USA
Status:
Offline
|
|
Is the "CODEX" tag not good enough as a workaround? It IS a pain to not be able to use some sort of "code" tag, but I've made do with other tags as needed. I do not think that we have yet tracked down WHY the built in tag no longer works. As to whether or not there's an urgency in applying updates, most of the updates I've looked at were security or usability fixes, not just "here's a cool new feature that three people in the whole world will ever use" things.
|
Glenn -----OTR/L, MOT, Tx
|
|
|
|
|
|
|
|
Mac Enthusiast
Join Date: Nov 2002
Location: More Cowbell...
Status:
Offline
|
|
Originally Posted by ghporter
Is the "CODEX" tag not good enough as a workaround? It IS a pain to not be able to use some sort of "code" tag, but I've made do with other tags as needed. I do not think that we have yet tracked down WHY the built in tag no longer works. As to whether or not there's an urgency in applying updates, most of the updates I've looked at were security or usability fixes, not just "here's a cool new feature that three people in the whole world will ever use" things.
I'm not sure how the original [code] tag worked, but CODEX does not provide for whitespace at the beginning of a line. i.e.- here is some spaced/indented code:
[codex]
int main() {
for(int i=0; i<10; i++) {
cout << i << endl;
}
}
[/codex]
now replace the white space at the beginning of the lines, with the - character, and you get what you are supposed to see:
[codex]
int main() {
----for(int i=0; i<10; i++) {
--------cout << i << endl;
----}
}
[/codex]
The second version of the code is much more easily readable.. the first version had the proper whitespace, but the CODEX tag does not replace whitespace with something like an to preserve whitespace at the beginning of a line.
For an example of how unreadable code can be with this codex tag, just take a look at the code I posted in the "accelerate framework" question in the developers forum. Without whitespace, it becomes quite unreadable.
|
|
|
|
|
|
|
|
|
Clinically Insane
Join Date: Jun 2001
Location: planning a comeback !
Status:
Offline
|
|
As a workaround, you can use a hard space (ALT + 255).
1
2
3
4
-t
|
|
|
|
|
|
|
|
|
Moderator Emeritus
Join Date: Mar 2004
Location: Copenhagen
Status:
Offline
|
|
Alt + 255?
You need to quit that job of yours, turtle. Windows is getting to you.
(Using the Danish keyboard layout in OS X, Alt + Space gives a hard space; not sure if it’s the same on an American layout, and I’m too lazy to check)
|
|
|
|
|
|
|
|
|
Clinically Insane
Join Date: Jun 2001
Location: planning a comeback !
Status:
Offline
|
|
Originally Posted by Oisín
Alt + 255?
You need to quit that job of yours, turtle. Windows is getting to you.
Haha, LOL, you are right.
I'm at work, and unfortunately, stuck with Windows.
I have no freaking idea how to do that on OS X, to be honest.
-t
|
|
|
|
|
|
|
|
|
Addicted to MacNN
Join Date: Mar 2006
Location: California
Status:
Offline
|
|
someone's not paying attention
|
|
|
|
|
|
|
|
|
Clinically Insane
Join Date: Jun 2001
Location: planning a comeback !
Status:
Offline
|
|
Originally Posted by brassplayersrock²
someone's not paying attention
Oh, yeah, sorry for that. I just looked at my DANISH keyboard.
Since I was hungry, I just eated it, even before I could notice the hard spaces.
-t
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Forum Rules
|
|
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
|
|
|
|
|
|