Closed JulianTonti closed 8 years ago
Interestingly, If I open a file in term3 using open -a Atom filename
then the error does not occur.
The error only occurs if I type atom filename
, where atom symlinks to the atom.sh
script located with the Atom.app: /Applications/Atom.app/Contents/Resources/app/atom.sh
Located online here: https://github.com/atom/atom/blob/master/atom.sh
Thanks for the detailed bug report. It made it much easier for me to reproduce the issue.
This might be a bug in Atom. For some reason, process.env.NODE_ENV
is being unset, causing the error in findReactContainerForID()
. Term3 definitely doesn't mess with that.
OK, try the latest version of Term3 (v0.22.1). It works around this bug in Atom.
Updated to 0.22.1, restarted Atom and indeed the error is fixed.
Thankyou!
Atom Version: 1.8.0 System: Mac OS X 10.11.5 Thrown From: term3 package, v0.22.0
Normally, term3 has no problem sharing a Pane with other Tabs, even when the Tabs are other term3 instances. But under the following condition, another Tab in the same Pane as a term3 instance causes an exception that keeps re-occurring endlessly, even when the Pane is removed. Here's how to replicate it:
0: starting from a blank slate
1: create a term3 instance in any pane with
ctrl-option-t
, then use it to touch a file and open it in Atom (the file must exist for the error to occur).2: the file should open under a new Tab in the same Pane as the term3 instance.
3: now try to do anything at all in the editor (even clicking to focus, switch tabs or close tabs):
4: the error keeps re-occurring, even if the offending Pane is terminated:
Stack Trace
Uncaught TypeError: Cannot read property 'null' of undefined
Commands
Config
Installed Packages