What I have noticed is that the default Markdown bundle doesn't
support some syntax features of Markdown Herein the Markdown
Preview,such as tables and strikethrough for example. Is there a
way of adding these extra Markdown Here features in the current
TextMate bundle so that they are properly viewed in the Preview?
I've tried to use the redcarpet Markdown bundle and the
Github-flavored Markdown bundle versions, which present some
highlighting within TextMate itself but fail to make the preview
work as well. I've noticed that one can add MathJax support with
the preference option TM_MARKDOWN_MATHJAX set to 1. Is there
something like that for extra Markdown Here syntax support?
In my master .tex file, the command LaTeX > Insert > Citation Based on
Current Word works fine.
However if I try to run the same command in the child files, I get a
dialogue box with the error message "Failure running ³Citation Based on
Current Selection². plus a long list of paths.
This is what I have set in Preferences > Variables:
Anyone know what the problem is?
I'm using TextMate as the editor for Git (writing commit messages and
similar). When I do a commit in the Terminal, I've fairly recently
started to notice that after I've written the commit message in TextMate
and closed the window Git still waits for TextMate. If I either open up
a new window in TextMate and closes that or quit TextMate, Git stops
waiting and finishes the commit.
I'm not sure if this is a problem with Git or TextMate. Has anyone else
experienced this problem.
OS X 10.10.3
git version 2.3.7 (Apple Git-57)
I am slowly migrating from 1.5, and one thing that I really liked about the former was that if you double-clicked a symbol :foo or instance variable @bar, your selection cursor only grabbed the name, not the metacharacter preceding it. This made it really easy to change the content without altering the shell. Several times lately I have been caught out by this difference in TM2 — there, a double-clck selection grabs the entire thing. Muscle memory is foiled.
Is there a place in the Ruby bundle syntax that controls this behavior?