CoffeeScriptLineMatcher
github.com
CoffeeScriptLineMatcher
1–10 of 11 posts
Re: CoffeeScriptLineMatcher
#2Re: CoffeeScriptLineMatcher
#3I feel like that's a pattern I see around here, which is odd because if you'd rather just use javascript that seems totally reasonable without an excuse.
Re: CoffeeScriptLineMatcher
#4Nice to see this, as it seems to address one of the most common concerns about using CoffeeScript. I have to wonder, though, how many minds will it really change? Maybe a lot, but I'm wondering how this will pan out. I'm guessing some people provide line matching for debugging as a concern but will continue to move the goal posts as this and other barriers are removed. I feel like that's a pattern I see around here,…
My hope is that it can help early adopters get over the initial debugging barrier, which, despite the hype, is a legitimate concern. The tool can also be an aid for advocates in teaching coffeescript.
Re: CoffeeScriptLineMatcher
#5Based on that, what would be even more useful still is a way to browse my code from a within the editor itself. Something with say line numbers on some left pane synchronized with the corresponding file section on the right pane.
Some editors already provide a similar feature using line numbers from compilers ; that's usefull to fix syntax errors typically.
Re: CoffeeScriptLineMatcher
#6Great. Based on that, what would be even more useful still is a way to browse my code from a within the editor itself. Something with say line numbers on some left pane synchronized with the corresponding file section on the right pane. Some editors already provide a similar feature using line numbers from compilers ; that's usefull to fix syntax errors typically.
https://github.com/showell/CoffeeScriptLineMatcher/issues/13
Re: CoffeeScriptLineMatcher
#7Re: CoffeeScriptLineMatcher
#8I just tried this out and the web interface it provides is awful. You're better off opening the .js and .coffee files in vi and finding things manually. The page is twice the width of my browser as I'm looking at it now.
elements. You could set the white-space to 'pre-line' for those elements to take care of the width issue.
Re: CoffeeScriptLineMatcher
#9I just tried this out and the web interface it provides is awful. You're better off opening the .js and .coffee files in vi and finding things manually. The page is twice the width of my browser as I'm looking at it now.
I think you should fork it and rewrite the CSS for the dashboard. The markup for the code snippets is just elements. You could set the white-space to 'pre-line' for those elements to take care of the width issue.
Re: CoffeeScriptLineMatcher
#10Nice to see this, as it seems to address one of the most common concerns about using CoffeeScript. I have to wonder, though, how many minds will it really change? Maybe a lot, but I'm wondering how this will pan out. I'm guessing some people provide line matching for debugging as a concern but will continue to move the goal posts as this and other barriers are removed. I feel like that's a pattern I see around here,…