How do I properly format my data w/out it being screwed with by the markup?
Some of my story text is messed up with the markup language.
I have some sample code and in it you'll see something like
*** blah text goes here ***
the markup being used automatically converts that to bold.
I'd very much like to use something like
I have some sample code and in it you'll see something like
*** blah text goes here ***
the markup being used automatically converts that to bold.
I'd very much like to use something like
or
or really anything so it doesn't strip away things like this.
This is the only formatting problem I've noticed so far but
I'm sure there are other markup problems -- I don't think
having to escape it is the answer here.
2
people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
-
Inappropriate?wow! even get satisfaction is turning my triple stars into markup -- this is fucking brilliant...
the orig. text is like so:
without the escape characters of course
\*\*\* adsfadf \*\*\*
how do I surround my text without having the markup screw it up?
I’m frustrated
-
Inappropriate?Hear, hear! Please let me turn off Markdown, or at least provide escapes.
In CL global variables are typically named *foo*, which means that every time one is mentioned it becomes bold.
I’m frustrated
-
Inappropriate?you forgot to mention that not only does it turn bold but then you have to re-format the code with the asterisk that got taken... this is such a pain in my ass
I’m not pleased
-
Inappropriate?wow... I don't have this problem (because I don't paste in markup) but if I did I'd be frustrated. I'm voting for it.
I imaging there a workaround similar to the process I use to share all of my design deliverables. *I never attach anything to a tracker story* (even though I'm one of the people you can blame for requesting the attachment feature). Instead, all of my reference materials live on a server that is easy to update Changing tracker stories every time i make a refinement is a lot of overhead that I don't have time for and version control is nice to have.
Maybe you guys could keep txt files in your repository then link to that file in your tracker story.
Workaround aside, I agree that there should be a way to quote code. There isn't? -
we have plenty of tests that go through our continuous integration all the time that have the files we post -- however in my use case I have a program that posts a story for a NEW test that needs to be written cause something 'bad' happened -- this is all automated and the latter that you mentioned would be such a overly complex problem to something as simple as allowing text-as-is to be put into the story -- it just seems like this is something that should be inherent considering there is mark-up to begin with..
Loading Profile...



