I'm currently setting them up with Sublime Edit, but it's not quite ideal as it's overly complex for what they need and I still have to manually configure it to default to UTF-8.
Many people care more about rendered markdown than about raw markdown, and would prefer to edit closer to the rendered result than to the human readable but not what they're interested in text. For those people, this eliminates the "write - render - check" cycle.
If there was an equivalent of ckeditor or tinymce that could output markdown or textile instead of html, I'd find that extremely useful.
I presume you edit the document in the 'rendered' view (as opposed to the plain text), probably like in a word processor where apply formatting by selecting text and clicking buttons or pressing key-combos -- but I don't think there's anything there that clearly indicates that.
There's some degree of mixed-messages with the way in which it mentions/shows plain-text and markdown.
As for Markdown parts – Texts 0.3 supports only blocks of plain text, headers (setext), unordered lists, code and math blocks (pandoc extension) and intervals of bold, italic, code, math and links. Only simple links (<URL>) are supported for now.
The idea is to expand syntax gradually, focusing on simplicity of user interaction. There are too many flavours of Markdown out there and several ways of writing the same structure in Gruber's Markdown is not a good thing, IMHO. There is no real need to decide between _italic_ and italic.
The object model of the text that is implemented is as simple as possible: blocks and spans (without nested spans). It shouldn't be a problem to implement essential parts of AsciiDoc and other plain text markups. When these formats get into the product depends on the interest from users. I'm planning to expose an API to allow implementation of formats as plugins.
Note: it doesn't recognize .md or .markdown file extensions on OSX
Would be nice if it did, for authoring blog posts to be used with Jekyll
When line is active, edit markdown source, else display rendered line.
Support for inline LaTeX editing is a bonus.
But switching code block style (Cmd+3 on Mac or Ctrl+3 on Windows) on and off maintains inline syntax. So you can type raw Markdown into a code block and then switch it into plain text paragraph with formatting.
This can be also done in source code mode. For example, select few words, select Bold from the menu, then these words are wrapped in
1. If it becomes really popular, you can make video tutorials and sell ads on your site 2. You can consider making it donation ware
There really isn't much options to build revenue streams around a FOSS text editor Its a tuff area
Pity. Just what I was looking for.
1) How do I make several levels of headers (#, ##, ###, ####)? This is what I use markdown for the most - nesting texts in clearly visible subsections. In the menu I can only see only one header, and in the screenshot I see two (==== and ---).
2) Rendering the PDF side-by-side would be useful. If I understood correctly one currently has to compile to PDF manually, which sort of defeats the purpose of a GUI app.
1) Tab/Shift+Tab change the level of header.
2) Yeah, it's "not implemented yet" :) Actually, there are many ways to publish from Markdown, including services like scriptogr.am. So I'm not sure that compiling PDF is the most important feature.
Good to have alternatives, especially for the Windows platform.
They have Django template syntax mixed in, so for example:
{% extends "_foo.html" %} {% block article %}
MarkdownPad seems to manage to convert the markdown bits just fine.
If I need a Markdown editor, it's awfully handy to be able to type as Markdown and see it rendered on the fly.
How much is missing?
