Hi,
I have some small suggestions to the HTML, CSS and Markdown Bundle.
# HTML
## Refresh Running Browser(s)
Change Scope to `text.html, source.css` so the Browser can be refreshed when editing the CSS file.
## Minor syntax stuff
php-source = { patterns = ( { name = 'comment.line.number-sign.ruby'; match = '#.*?(?=?>)'; }, { name = 'comment.line.double-slash.ruby'; match = '//.*?(?=?>)'; }, { include = 'source.php'; }, ); };
Ruby mixed with php?
# Experimental/CSS
What about those Experimental Bundles? I use the CSS syntax from there and it would be nicer if it was in the CSS bundle. Because calling the Gear (Bundle Stuff) menu (Control-Escape) puts you there and not in the CSS bundle. The experimental CSS syntax has been around for quite some time and I wonder if it still is work in progress? It seems to be better than the official CSS Syntax anyway.
# Markdown
## Suggestion: Markdown with [SmartyPants](http://daringfireball.net/ projects/smartypants/)
“Preview”/“Preview in Browser” or “Convert Document/Seletion to HTML” Pipe it through `Smartypants.pl` (must be added to the repos.) to have nicer HTML. There should not be any problems so one could add it to the default commands instead of creating an additional variant with SmartyPants. I wonder why John Gruber did not combine them in the first place.
# Conclusion
That's it for now.
Have a nice day, Soryu.
PS: Why do I not simply make those changes for myself? I did but then I won't be able to use better bundle items from the repository or even a new TextMate release because my changed override them. I know Allan has something on the todo to manage this but it's not short term.
On 12/1/2006, at 18:03, Soryu wrote:
# Experimental/CSS
What about those Experimental Bundles? I use the CSS syntax from there and it would be nicer if it was in the CSS bundle. Because calling the Gear (Bundle Stuff) menu (Control-Escape) puts you there and not in the CSS bundle. The experimental CSS syntax has been around for quite some time and I wonder if it still is work in progress? It seems to be better than the official CSS Syntax anyway.
Max can probably comment on this -- I think he had some reservations about making the syntax official, and I made some changes which lost all the ASCII plist comments (although they're still in the repository) which contained his to-do.
# Markdown
## Suggestion: Markdown with [SmartyPants](http:// daringfireball.net/projects/smartypants/)
“Preview”/“Preview in Browser” or “Convert Document/Seletion to HTML” Pipe it through `Smartypants.pl` (must be added to the repos.) to have nicer HTML. There should not be any problems so one could add it to the default commands instead of creating an additional variant with SmartyPants. I wonder why John Gruber did not combine them in the first place.
Is SmartyPants safe for code? I.e. I often have some form of code or data format listed in my Markdown files where " means " and ' means '. When I want “curly quotes” I type that. Though I don't use the nicer ’ character.
On 24.01.2006, at 04:44, Allan Odgaard wrote:
# Markdown
## Suggestion: Markdown with [SmartyPants](http:// daringfireball.net/projects/smartypants/)
Is SmartyPants safe for code? I.e. I often have some form of code or data format listed in my Markdown files where " means " and ' means '. When I want “curly quotes” I type that. Though I don't use the nicer ’ character.
SmartyPants does not modify characters within <pre>, <code>,
<kbd>, or <script> tag blocks. Typically, these tags are used to display text where smart quotes and other “smart punctuation” would not be appropriate, such as source code or example markup.
It worked fine for me with my documentation.