![Sad :(](./images/smilies/icon_e_sad.gif)
I can deal with it.. I m using the RSS feature to go through the UnRead stuff
![Smile :)](./images/smilies/icon_e_smile.gif)
On the Pc I use "the Old Reader".. Then I got Feedler to connect to "The Old Reader".
Result, it's like having a mobile client of the forum
![Very Happy :D](./images/smilies/icon_e_biggrin.gif)
YES IT WAS. outright maliscioussinkfaze wrote:Does anyone know what it would take to get the code formatting back to the way Chris originally had it on this type of forum? It wasn't perfect but at least you could distinguish code from comments.
Poly disallowing color tags inside code tags was one of his more destructive acts.
Correct me if I'm wrong, but from looking at the GESHI docs, it appears to be able to create links using keywords. There is a whole section on that in the docs. The autohotkey.php language file appears to include some links already which point to the old site.tank wrote:... GESHI is supposed to support AHK but i was considering something even more fascinating
I want to scan the commands folder of the documentation( power of PHP ) and if something in a code block matches a command it becomes a hyperlink to that command doc. Its not a big deal to identify comments vs not comments.
As of version 1.0.2, GeSHi allows you to specify a URL for keyword groups. This URL is used by GeSHi to convert the keywords in that group into URLs to appropriate documentation. And using add_keyword_group you can add functions and classes from your own projects and use the URL functionality to provide a link to your own API documentation....You may be wondering how to make each keyword in the group point to the correct URL. You do this by putting {FNAME} in the URL at the correct place. For example, PHP makes it easy by linking http://www.php.net/function-name to the documentation for that function, so the URL used is http://www.php.net/{FNAME}.