I rarely touch that code, I haven't made any changes to that for almost two years (I just properly generated that patchfile, so I can update nagelfar but still keep my changes). I'll try to remember to change the paste above and post here that I updated it. (So having this thread on your watchlist should do). It's not worth putting that into a CMS

Had an interesting experience with the site today... was giving a script to a friend when upon pasting, it reported a missing brace. I was quite sure there was no missing brace, as my script works perfectly, so I spent time tracking it down to the section and discovered it was this regex causing the error: {([[:alnum:]]+)[-./\\]*\1+} What happened, is that the site tried to escape the ] rather than the backslash in that regex. It doesn't see the escape as "\\". I even tried a single \ and it still tried to escape the ]. Adding another ] clears it, but will also break the script if loaded.

The warning is actually generated by pretty simple code (not even close to what would be required to do that perfectly) and shouldn't even be there anymore, we just disabled it after you report. (the automatic syntaxchecker is way more accurate and replaces the need for that). However, the same bit of code is responsible for colorizing pairs or {} and [] and thanks to your bugreport we fixed that.

The closing ] in the regular expression is now the same as the one before (it used to be black).

I attempted to fix the line numbers not aligning properly with the code, depending on operating system + browser combination. While doing that, I also wanted to try out a new font for the code (which should work in all modern browsers, the 0 has a little dot in the middle to distinguish it from the O). Feedback is welcome!

Advanced options for this topic:

Ignore this topic(Do not list this topic in the "unread topics" search. You are currently not ignoring this topic.)Hide this topic(Hidden topics are not displayed in the topics list. This topic is currently not hidden.)