Hello all,
I am running Hyperterm 0.7.1.36 on OSX El Capitan 10.11.6.
When I start Hyperterm, the app opens but does not display anything within the console:
This problem has occurred since the first time I opened the app after upgrading to version 0.7.
I tried clearing the Hyperterm directory within _~/Library/Application Support/_ along with a restart, unfortunately to no luck.
Could someone help me? Thank you so much!
hxnt
All 3 comments
Hello @austinwade, are you able to join the HyperTerm slack? I think it would be easier to debug that way 馃殤
If not, can you open the Developer Tools, by pressing alt+cmd+i or go to View -> Toggle Developer Tools in the menubar?
馃憢
albinekb
on 31 Jul 2016
Chatted with @austinwade and found out what the problem was: https://github.com/zeit/hyperterm/blob/master/lib/components/term.js#L31
If you set cursorColor to anything that color can't parse, the error is not handled and results in a broken hyperterm 馃槶
So this needs to be taken care of 馃懠 to alert the user that the config is broken, and i would also suggest an option to reset the config to the default config.
A++ experience would be if hyperterm made a copy of the config everytime it works, so when it breaks the user can get a notification with an option to restore to the last working config.
albinekb
on 31 Jul 2016
I'd love to start contributing to this project, and this seems like a good place to start - there isn't much in the README in regards to contributing, so can I just crack on is there anyone who could point out some gotchas for me?
jwhitmarsh
on 4 Aug 2016
Related issues
alejandrofloresm
路
3Comments
aem
路
3Comments
ghost
路
3Comments
sagarduwal
路
3Comments
cooperpellaton
路
3Comments
Most helpful comment
Chatted with @austinwade and found out what the problem was: https://github.com/zeit/hyperterm/blob/master/lib/components/term.js#L31
If you set
cursorColorto anything that color can't parse, the error is not handled and results in a broken hyperterm 馃槶So this needs to be taken care of 馃懠 to alert the user that the config is broken, and i would also suggest an option to reset the config to the default config.
A++ experience would be if hyperterm made a copy of the config everytime it works, so when it breaks the user can get a notification with an option to restore to the last working config.