On: Atlassian, AU company raises US60M, unheard of for...

[goodside]

A few months ago, I wanted to insert a double backslash into a Confluence wiki page. This isn't as odd as it sounds; Windows network file paths begin with \\Foo\. Since backslashes are of course an escape char, you usually have to use \\\\ to get \\ to output. But, in Confluence, this outputs two newlines. Yes, double-backslash is the symbol for a newline.

Counter-intuitive, yes, but no worse than that so long as there's another symbol you can use for when you do need a double-backslash. But, the thing is, there isn't. When Confluence was first designed, they used up their only escape char with their nonstandard newline symbol. This is, their support staff informed me, a deep-rooted and unchangeable aspect of how Confluence works. It's not a bug, because it will never be changed.

This should give you the gist of what Atlassian is like.

[i386 → goodside]

Sorry you had a problem with Confluence. I can tell you that there is a project running right now to make the editor a lot nicer to work with. Not sure on the delivery schedule (I work on Bamboo so its not my product) but I believe it is on its way.

[daredevildave → goodside]

They must have fixed something, because in our Confluence wiki:

  \\ -> new line
  \\\\ -> \\\\
  \\Foo -> Foo
  \\Foo\Bar -> \\Foo\Bar

Somewhat errant result for \\Foo, but the other ones seem to work.

[goodside → daredevildave]

The \\Foo\ example I gave was poorly chosen, because they put in a kluge fix so that anything that resembles a Windows file path will pass through unparsed. You cannot use \\ in any other circumstance, which is why \\Foo failed.

[brown9-2 → goodside]

It might not help now, but I think you could have wrapped \\Foo\ with {noformat}\\Foo\{noformat}

[goodside → brown9-2]

This does not work. Nothing obvious will. This is an acknowledged issue that they are opting never to resolve. Here's a relevant issue on their bug tracker that has been open for four years: http://jira.atlassian.com/browse/CONF-6405

It wouldn't be nearly as infuriating if it weren't caused by such a terrible design decision (using doubled backslashes for line breaks when the backslash is your only escape char) in the first place.