You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if this is an issue or intended behavior. When you leave the web page that contains the text box being edited in a frame, is the behavior intended to be that the frame remains open? If I C-c C-c then the frame is closed, but just wondering if this is the experience that is intended.
Also - whenever I save C-x C-s the focus is changed to the top of the file...quite annoying. Is this intended as well?
Context: emacs 26.1 (text mode in terminal window) on Pixelbook.
Thanks
The text was updated successfully, but these errors were encountered:
Currently the connection to the edit-server is a single transaction - send contents, receive results. It's not well suited to handling these async actions like browsing away on the page.
The C-x C-s behaviour is a consequence of this communication process because you effectively save the results and then start a new session. I'm sure however we could do something to persist the cursor from the previous edit session.
The long term solution would be to replace the existing GET/REPLY approach with a fully bi-directional websocket between the browser and the edit server. This is the approach that Atomic uses for example.
Not sure if this is an issue or intended behavior. When you leave the web page that contains the text box being edited in a frame, is the behavior intended to be that the frame remains open? If I C-c C-c then the frame is closed, but just wondering if this is the experience that is intended.
Also - whenever I save C-x C-s the focus is changed to the top of the file...quite annoying. Is this intended as well?
Context: emacs 26.1 (text mode in terminal window) on Pixelbook.
Thanks
The text was updated successfully, but these errors were encountered: