Hello! Who is the maintainer of the bundle for Markdown? Looks like he is missing from the README in svn.
I noticed the regexp for emphasis
match = "[*]([^\\*]|\\.)*?[*]";
causes the engine to beautify the bulleted list
* normal *emph*.
with " normal " in italics instead of "emph". Do those TM regexps support some sort of precedence? Do they supoprt look-behind assertions?
In addition, the regexp for itemized lists looks too weak:
begin = "^\s*[*+-]";
According to the current spec it would be something like:
begin = "^ {0,3}[*+-][ \t]";
-- fxn
On Jun 16, 2005, at 6:44 AM, Xavier Noria wrote:
Hello! Who is the maintainer of the bundle for Markdown? Looks like he is missing from the README in svn.
I noticed the regexp for emphasis
match = "[*]([^\\\\*]|\\\\.)*?[*]";
In addition, the regexp for itemized lists looks too weak:
begin = "^\\s*[*+-]";
According to the current spec it would be something like:
begin = "^ {0,3}[*+-][ \\t]";
-- fxn
I just committed an update that should fix the unnumbered list and emphasis issues. Please test it and let me know if there are any problems, and any other changes that should be done.
In a related note, I think this has come up before, but in the markdown bundle, there are two files test-minimal.markdown and test.markdown. Why does TM refuse to open those files?
Also in that file, the 4th line or so is: _italic _ _
Now, if I understand correctly, this should not be italisized, right? Haris
On Jun 17, 2005, at 0:03, Charilaos Skiadas wrote:
I just committed an update that should fix the unnumbered list and emphasis issues. Please test it and let me know if there are any problems, and any other changes that should be done.
Fixed, thank you for such a quick update!
-- fxn
On Jun 17, 2005, at 0:03, Charilaos Skiadas wrote:
In a related note, I think this has come up before, but in the markdown bundle, there are two files test-minimal.markdown and test.markdown. Why does TM refuse to open those files?
TextMate will only open known text files by default (for projects). So for extensions it doesn't know about, you'll have to manually educate it by control-clicking the item and tell TM to treat it as text.
In 1.1b13 I have extended the learning heuristic so that if a file is opened stand-alone in TM, it will remember that the file type is text in the future.
But I probably will change it in the future to something like a blacklist, whitelist and a test of non-printable characters for unknown filetypes.