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
vim-session does not currently mark a session as dirty if the working directory changes. This means that if I open a session, 'cd' (or 'lcd') and then close the session, the updated session, with new working directory, will not be saved.
Out of curiosity, what is the reason for the dirty flag? Is it mainly so that users with autosave disabled won't get spurious save prompts?
My current thinking is that this feature may cause more problems than it solves. Dirty checks only check if the buffer list or layout have changed, which misses a lot of options that get saved with the session.
The text was updated successfully, but these errors were encountered:
I never liked this code and the additional complexity it introduced, so
lets try without for a while and see if anyone complains. If I really want
to I can always get the code back from version control.
Pull request #37: #37
Issue #38: #38
vim-session does not currently mark a session as dirty if the working directory changes. This means that if I open a session, 'cd' (or 'lcd') and then close the session, the updated session, with new working directory, will not be saved.
Out of curiosity, what is the reason for the dirty flag? Is it mainly so that users with autosave disabled won't get spurious save prompts?
My current thinking is that this feature may cause more problems than it solves. Dirty checks only check if the buffer list or layout have changed, which misses a lot of options that get saved with the session.
The text was updated successfully, but these errors were encountered: