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
Basically when you are in development mode (with watch on) editing the content will usually cause the page to jump to another fixed location. When you are writing latex, this is more painful as you are kind of using the page to check if it compiled and iterating on that.
I'm wondering if anyone has thought about this or if it possibly to avoid.
I have not dug into it yet but was hoping someone had some clues as to what is setting this starting point. It seems consistent across two browsers that I tested it on.
Obviously not a huge deal but I would dig into it if someone had a good guess as to where to start.
The text was updated successfully, but these errors were encountered:
Basically when you are in development mode (with watch on) editing the content will usually cause the page to jump to another fixed location. When you are writing latex, this is more painful as you are kind of using the page to check if it compiled and iterating on that.
I'm wondering if anyone has thought about this or if it possibly to avoid.
I have not dug into it yet but was hoping someone had some clues as to what is setting this starting point. It seems consistent across two browsers that I tested it on.
Obviously not a huge deal but I would dig into it if someone had a good guess as to where to start.
The text was updated successfully, but these errors were encountered: