Is your feature request related to a problem? Please describe.
I am GM in a TTRPG campaign (stuff like Dungeon And Dragons), and my notes are in markdown format
During the game, i switch between several open files, in the same window.
When i am, say, scrolled to a specific chapter in file A, but then need to check up on the players sidequests in file B, i switch to another file, and then back... and file A is at the start of the file, needing to scroll back to the specific chapter
Describe the solution you'd like
Remember and restore, for the current session, for files that have been opened, which position the user was last scrolled at
Describe alternatives you've considered
Splitting into smaller files, which displaces the problem onto switching between a lot of files. Which works, but having an upper ceiling in length is a bit annoying
Additional context
It is fine if not implemented. This would simply be a small, smart improvement, though as a dev of my own i can see the overhead in time to spend to maintain an "invisible feature" such as this one
Is your feature request related to a problem? Please describe.
I am GM in a TTRPG campaign (stuff like Dungeon And Dragons), and my notes are in markdown format
During the game, i switch between several open files, in the same window.
When i am, say, scrolled to a specific chapter in file A, but then need to check up on the players sidequests in file B, i switch to another file, and then back... and file A is at the start of the file, needing to scroll back to the specific chapter
Describe the solution you'd like
Remember and restore, for the current session, for files that have been opened, which position the user was last scrolled at
Describe alternatives you've considered
Splitting into smaller files, which displaces the problem onto switching between a lot of files. Which works, but having an upper ceiling in length is a bit annoying
Additional context
It is fine if not implemented. This would simply be a small, smart improvement, though as a dev of my own i can see the overhead in time to spend to maintain an "invisible feature" such as this one