R.J. Steinert

Ok, I found what might be a temporary fix. I turned off the "Convert URLs into links" filter for the "Markdown Syntax and HTML" text format. There might be a way to make the "Markdown" filter and the "Convert URLs into links" filter work harmoniously but for now we'll role without the "Convert URLs into links" filter. We'll look into some WYSIWYG like buttons down the road that will help folks create the necessary markup without needing to remember all of the syntax quirks. For example, there could be a button that you press that then prompts the user for a URL and text and then inserts the proper syntax. It's not true WYSIWYG but this technique makes the learning curve for the syntax easier to climb. If this is the first time you've heard of WYSIWYG, it's a program that sits inside of a text box on a webpage that makes the text box act like Microsoft Word. Unfortunately it creates nightmares when used for documentation. Things like diffing (comparing) versions of a Wiki page become incomprehensible, you can never get what's in the WYSIWYG to look like what it actually spits out, and if you ever change the settings on a WYSIWYG you risk breaking every piece of documentation when you go back to edit it. WYSIWYGs do however work really well for writing blog posts that you only (theoretically) edit once and then is set in stone. WYSIWYG example using the LATEX syntax from Wikipedia's page on WYSIWYGS:

Thanks for explaining further Louis. I see there is still an issue with that way of making links at the moment so I'll try to work the kinks out right now.

Ah, you just found a bug. I think I fixed it, go ahead and try that link again.