In order to write the "grammar" for this bundle from scratch, I have had to grapple with learning about TextMate grammars. But this was quite unnecessary, because although Markdown may be said in some weird way to be based on HTML, AsciiDoc most certainly is not. For example, the previous Asciidoc bundle's grammar, copying the Markdown bundle, was scoped as this caused all kinds of havoc, because it allowed the HTML TextMate bundle to reach into the AsciiDoc bundle and affect such things as styling and indentation in a particularly horrible way. Many of the problems with the previous AsciiDoc bundle were caused by incorrect assumptions, mostly having to do with the fact that it was based on the Markdown bundle, which was a huge mistake, as AsciiDoc is not particularly like Markdown and is certainly not related to it. Problems, Solutions, and PhilosophyĪn advantage of writing the grammar entirely from scratch is that I was able to make a completely fresh start. This is the result: a new AsciiDoc bundle, written from scratch, in which I can maintain and write my books. At that point, the old AsciiDoc bundle began to behave very badly, and I decided to write my own. This caused my Ruby-based TextMate projects (such as RubyFrontier) to behave badly, until I also adopted TextMate 2. ![]() Then, however, Mac OS X 10.9 ("Mavericks") arrived. ![]() It had some quirks and shortcomings, but I could live with them. Previously, I was using the Zuckschwerdt AsciiDoc bundle for TextMate with a few changes to add missing features and to make it less crashy, it has served me fairly well under TextMate 1, through thousands of pages and four editions of my books (currently iOS 7 Programming Fundamentals and Programming iOS 7). The purpose of this bundle is to provide a working milieu for editing AsciiDoc in TextMate 2. A New AsciiDoc Bundle for TextMate 2 Ground of Being
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |