I guess this is a two-part question:
1. Why weren't `<` and `>` included as a smartTypingPair for Markdown? Since those are the characters used to surround in-line URLs that should become clickable links, it seems like it should be there so you could just highlight a URL and type `<`. This seems pretty obvious though, so maybe this pair was omitted intentionally for some reason I haven't caught onto?
2. Since the scope in Markdown includes `text.html`, why doesn't that pair get pulled from the HTML bundle's preferences? Is it because there are explicitly defined pairs for a more specific scope in this case (`text.html.markdown`)?
Just curious. Thanks.
Rob
Rob McBroom wrote:
Why weren't `<` and `>` included as a smartTypingPair for Markdown? Since those are the characters used to surround in-line URLs that should become clickable links, it seems like it should be there so you could just highlight a URL and type `<`. This seems pretty obvious though, so maybe this pair was omitted intentionally for some reason I haven't caught onto?
Sure. 1) For saying things like things like 5 < 6, where I definitely don't want an automatic > typed for me, and 2) markdown uses > to denote block quotations, and I don't want TM thinking those are part of a bracketed pair.
Feel free to change your local preference item that sets this.
Is it because there are explicitly defined pairs for a more specific scope in this case (`text.html.markdown`)?
Yes.
-
Jacob Rus -
Rob McBroom