I'm not as invested anymore, but I'm curious about this. What is your most-used tool for figuring out problems in code? Honest answer.
-
-
It can be a powerful workflow, but I'm curious if a better console would be good enough for some of your needs?
-
didn't Firefox try the hell out of this? I'm a visual learner is the issue, I think.
-
the gcli? Not quite what I'm thinking. Execution is important. Still, everyone is different!
-
I tend to be a bit of a visual explorer, but a console that also moved around a context pane might work really well for me.
-
I prefer navigating via console (like in gdb or pry) but don't feel grounded without a persistent UI of "where you are"
End of conversation
New conversation -
-
-
i.e. from console, ability to search & find code, set tracepoints (https://sourceware.org/gdb/onlinedocs/gdb/Tracepoints.html …), etc
-
I wish GCLI was much more integrated: into console, ⌘⇧P menu...
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.