Amin Ya

Results 1114 comments of Amin Ya

One other thing I noticed is that running `clear` doesn't set scrollback to 0, while this happens if you try it on Windows Terminal.

When I start an Atom session, I expect the terminal to start again if it was open. Similar to how Atom recovers the open text editors.

Yes, I do have it checked. This is random though. Sometimes it works! I will try to get some reproduction steps.

This is what I mean. I need to close this and start a new one: ![image](https://user-images.githubusercontent.com/16418197/96354710-46e21c00-109f-11eb-8bd5-5f292de8d1be.png)

There are no errors. It just does not show anything. It is like an empty pane (like in #5) There is no element to choose: ![image](https://user-images.githubusercontent.com/16418197/96356738-b6b0d080-10b8-11eb-9738-2d36cdb908bd.png)

Sure. I can add the logs. I am using the latest nightly.

I had a terminal open in the bottom dock, I minimized it. Closed Atom, and opened it again. The pane was empty: ![image](https://user-images.githubusercontent.com/16418197/96357615-f03b0900-10c3-11eb-8f44-79057f677d64.png) Not minimizing the terminal before closing fixes...

How can I get more information about `entries`? This seems like an xterm thing. Let me see if I can debug into xterm

This is what happens when I try to debug inside the IntersectionObserver callback: ![image](https://user-images.githubusercontent.com/16418197/96357993-182c6b80-10c8-11eb-9d9e-77811cfa2a4d.png) If I click keep it open: ![image](https://user-images.githubusercontent.com/16418197/96358018-43af5600-10c8-11eb-9431-ef37e78e84d1.png)

The issue is not still solved. You mentioned you can hack something using `setTimeout`. Can you look into that? @UziTech