Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

verbatim text (curly braces) #29

Open
MadEarl opened this issue Jun 9, 2020 · 4 comments
Open

verbatim text (curly braces) #29

MadEarl opened this issue Jun 9, 2020 · 4 comments

Comments

@MadEarl
Copy link

MadEarl commented Jun 9, 2020

Does anyone else have the problem that Jira verbatim text is not converted?

When I have
~Example Text~ in org, it gets converted correctly to {{Example Text}} in Jira, but when converting from Jira to org, the replacement does not occur, the curly braces end up in org and are converted to Jira markup on the next push, so that the text in Jira subsequently is garbled.

I have checked the regex pattern, it seems ok. I am at a loss as to why the transformation does not happen.

@johnhamelink
Copy link

I've just started using ejira, and I've noticed it does this also. A JIRA project I've imported makes heavy use of the {color:#00b8d9}Example{color} syntax. I don't know if it's possible to support coloured text, but it'd be nice to at least hide the syntax so it's not visible in emacs.

@nyyManni
Copy link
Owner

Colored text was something I also ran into, but did not end up implementing as there was no support for it in the org-mode. It would be really nice if I could at least edit an issue description, which already has coloring - without destroying it.

Creating a body of text with coloring in org-mode would probably require extending org syntax itself.

@johnhamelink
Copy link

It's not the end of the world - just being able to escape JIRA's UI is a huge win on its own :) But a nice to have!

@MadEarl
Copy link
Author

MadEarl commented Jun 23, 2020

I fixed the {{}} issue; if it by itself is causing trouble for others, I can make the fix available. IIRC, it had to do with replace-regex-in-string misbehaving in certain circumstances, so I replaced it with a similar function from the s package. My fork has the change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants