-
Notifications
You must be signed in to change notification settings - Fork 30
Support for git branches need to be considered. #6
Comments
The intent behind co-locating these artifacts with a given folder/repo is to avoid orphaned data and to emphasize the scope to a working directory. There are a few measures in place that would make something like transitions between branches fairly seamless. so can you expand on what you mean by "not comfortable", and what problem it is you're wanting to solve by having a specialised directory? |
I understand the intention. What I said "not comfortable" is that when switching from this branch to another, I want to load the workspace of that branch, not the one of the former branch. |
Interesting idea, that makes sense - so essentially git support for sessions that auto-reload based on current branch. I'll keep this issue open as a feature request and will work on it the next opportunity I have. Thanks for your feedback! |
Looking forward to that !
…On 2017年8月18日 +0800 PM3:49, Thaer Khawaja ***@***.***>, wrote:
Interesting idea, that makes sense - so essentially git support for sessions that auto-reload based on current branch. I'll keep this issue open as a feature request and will work on it the next opportunity I have. Thanks for your feedback!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Sorry to dig this up after almost 3 years but since the issue is still open... is this still on the "roadmap"? |
+1 for this feature |
never mind, got it all worked out |
Placing .session.vim and .undodir under the current path is easy to manage sessions, but all git branches have to share the same session, which is not comfortable.
Maybe putting all sessions into a specialized dir is better ?
The text was updated successfully, but these errors were encountered: