It's not the same without you
Join the community to find out what other Atlassian users are discussing, debating and creating.
I was trying to show someone how to use the {code} tag in a comment in Crucible. I want to wrap my example in code tags, but have the literal "{code}" show up in the example.
Hey girl, I heard you like putting code in your comments.
{code}
\{code\}
// Your code goes here. \{code\}
{code}
And this is how it came out:
Hey girl, I heard you like putting code in your comments.\{code\} // Your code goes here. \{code\}
How can I enter the comment so that it appears like this?
Hey girl, I heard you like putting code in your comments.{code} // Your code goes here. {code}
Jason, you are right, it does not work with {code} tags. It does work for the problem that Patrick was having: Hey girl, I heard you like putting code in your comments. {code} // Your code goes here. {code} As far as I know, in {code} tags there is no need to escape curly braces. You might need to put the actual tag in it's own line: {code} { "Name": "Somename" "Lastname": "Somelastname" } {code}
This solution works if you don't mind your text being bold:
example 1:
{foo}
example 2:
{{code}}
This absolutely works and was the only way I could enter the regex "[- 0-9_\p{Ll}\p{Lu}\p{Lt}]" into a JIRA comment ... though in raw it does look like this: *"[- 0-9_\p**{**Ll**}**\p**{**Lu**}**\p**{**Lt**}**\]"*
Sigh. I can't figure out how to enter code in the question so it doesn't create several disjointed code blocks.
You guys, this would be so much easier if you just got rid of these proprietary markup languages and switched to Markdown.
With underscores, one can backslash an underscore mid-underline-section to get a literal underline there. With double curly braces around code, one cannot backslash a close-curly-brace mid-code-section to get a literal close-curly-brace there.
Example without proper escaping:
{{my_dict = {}}} renders as my_dict = {
}
Example attempting to use a backslash to escape the close-curly-brace (which doesn't work):
{{my_dict = {\}}}
renders as my_dict = {
}
Is there a sane alternative that works in this case?
I'm not seeing one in the other answers to this question. The double-star trick mentioned in another answer does not work in the case of code sections (delineated with double curly braces).
The trick I have found to work is to close the curly brace section early, then put the single close-curly-brace in its own code section. Thus, the workaround to get one close-curly-brace in your code section is the mind-numbing sequence of:
}}{{}}}
That'll put a close curly brace at the end of a code section. You'll need to reopen the code-section with a {{ after all of that if you're not yet at the end of your code section.
Example of the functioning workaround:
{{my_dict = }}{{}}} renders as my_dict = {
}
There really needs to be a better way.
Another vote for switching to Markdown! It shouldn't take half an hour to find a way to get a close-curly-brace in a code section. Backspace escaping should work for code sections like it does for underscores in underline sections. The JIRA markup language is as inconsistent as it is buggy.
You could try doubling the curly braces. So, you type "{{" and "}}" instead of "{" and "}".
I am not sure if that will work in Crucible, but I know it works on JIRA comments and descriptions.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.
Read moreHi Community! Kesha (kay-sha) from the Confluence marketing team here! Can you share stories with us on how your non-technical (think Marketing, Sales, HR, legal, etc.) teams are using Confluen...
Connect with like-minded Atlassian users at free events near you!
Find a groupConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.
Start an AUGYou're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.