-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: possible to link based on currently active git branch? #15
Comments
Could be as an option. The default locations (project, dir and buffer) are merely examples. It basically comes down to writing custom methods |
OK, I might look into those keywords and some elisp later (tho pretty much
a noob with elisp :P). I suppose using two directories each with different
branches of the same project might work -- but it'll lead to many, many
open files almost with the same name (confusion, mess). If you imagine
working on 3-4 branches (which I do); the mess is even greater. x) A
workflow where a single key combo changes git branch and sesman instantly
picks up on this would be superior in some cases, I think.
…On Sat, Feb 9, 2019 at 4:09 PM Vitalie Spinu ***@***.***> wrote:
Could be as an option. The default locations (project, dir and buffer) are
merely examples. It basically comes down to writing custom methods
sesman-context and sesman-relevant-context-p. But I don't quite
understand the use case. Could you please elaborate a bit?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#15 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAFmmES7g-vAYjfYe-upX8UoL6ffDlCNks5vLtaMgaJpZM4ayWCB>
.
--
Mvh,
Lars Rune Nøstdal
quanto.ga -- algorithmic trading and investment systems; ideas, research
and development.
|
I see. This is an interesting feature. If emacs has a built-in ability to retrieve the current git-branch then implementing this should be a triviality. |
..not sure this is the right place to ask, but yeah would be a super cool thing.
The text was updated successfully, but these errors were encountered: