Ullyses III vs Marked
I've been using Ullyses III for pretty much all my writing, and in general I love it. However, U3 and Marked aren't playing nicely together, and I'm not sure which is the problem.
Here's the situation. If I write a file in U3 and export it to Markdown, paragraph breaks aren't creating <p></p> I've attached a file showing examples. The problem seems to be that when marked interprets a markdown file, it wants *two* crlfs to separate paragraphs. I'm unsure what the "correct" behavior is.
- Introduction.markdown 1.63 KB
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
1 Posted by chasrmartin on 23 Jul, 2013 04:40 AM
I've now created an account, and this time I think I have the full example I talked about.
Support Staff 2 Posted by Brett on 14 Aug, 2013 01:14 AM
Sorry for the delayed response on this one, got lost in my queue.
A double line break is always needed in Markdown to create new paragraphs. You can enable
<br>
tags on line breaks in preferences, but creating<p>
tags requires the extra line break.Is Ulysses recognizing these as paragraphs?
3 Posted by chasrmartin on 14 Aug, 2013 01:37 AM
Hi, Brett, I can relate on the email queue, believe me.
Yeah; I've been back and forth a couple of times with the U3 guys about
this, including finally copying them the appropriate excerpt from the
Markdown spec. Basically, if you use their markup, either straight
markdown or their markdown-with-metadata they call Markdown XL, the display
code recognizes a single newline as a paragraph: if you have enabled
inter-paragraph space and initial indents in your preferences, you get an
apparent paragraph break.
If you export the text to HTML from U3, it makes them properly-marked
paragraphs. But if you export markdown, it exports them with a single
newline at the graf breaks.
The solution, delivered I'm sure in a proper Prussian accent, is that if
you want to have full-fledged markdown, you need to put in two line breaks
yourself. (Strictly they're in Saxony, but call it artistic license.)
Not a terrible issue, once I figured it out, but less than well documented.
It's kind of a shame. I like the U3 model for managing text; I'd like to
use MultiMarkdown; Composer doesn't let me manipulate parts and such as
well as U3; Marked is a much better preview and formatting engine. I could
probably hack a U3-like interface in EMACS, but I don't have lots of time
for extra-curricular hacking any more.
In any case, you can close this ticket; it's not your problem, it's U3's.
Regards
Charlie Martin
Brett closed this discussion on 14 Aug, 2013 01:45 AM.