println and LightTable
Closed this issue · 6 comments
Because we are using LightTable, I find myself never using println in any examples. At a traditional REPL, we'd see the output of println, but in LightTable, println output shows in the console, which is hidden by default, and we see the results of calling a function inline.
Is this ok? Using println seems to be a big part of my day when developing, but I've just started using LightTable full time, and it might not be that important.
I'd love to see input from @bridgethillyer, @flyingmachine, @seancorfield, and @7maples on this.
I have added the following user behavior to open console in a tab at startup:
{:+ {:app [(:lt.objs.app/run-on-init [:console-tab])
...
This gives me an easy way to see the console output alongside my code evaluation.
I generally have at least two tabsets with console and browser in one and code in the other.
Sean
On Feb 8, 2014, at 2:05 PM, "Clinton N. Dreisbach" notifications@github.com wrote:
Because we are using LightTable, I find myself never using println in any examples. At a traditional REPL, we'd see the output of println, but in LightTable, println output shows in the console, which is hidden by default, and we see the results of calling a function inline.
Is this ok? Using println seems to be a big part of my day when developing, but I've just started using LightTable full time, and it might not be that important.
I'd love to see input from @bridgethillyer, @flyingmachine, @seancorfield, and @jen7maples on this.
While using LightTable so far, I have not been able to avoid using the console. Sean's suggestion seems like a good way to manage things for the workshop experience. We are packaging settings/user behaviors to distribute to the attendees, right?
FWIW, I don't use the console as much when working with LightTable, but being able to slap in println for debugging is still useful sometimes... :)
Sean
On Feb 8, 2014, at 3:14 PM, bridgethillyer notifications@github.com wrote:
While using LightTable so far, I have not been able to avoid using the console. Sean's suggestion seems like a good way to manage things for the workshop experience. We are packaging settings/user behaviors to distribute to the attendees, right?
Ok, thanks. I'll try to figure out somewhere to put it in there.
@seancorfield I did not know about putting your console in a tab. That is way better than the bottom of the screen.
Running through the curriculum today, and I have not had the need to print anything to the console. So maybe this is moot for the curriculum?
Close?
I think so.