Matthieu Moy <[EMAIL PROTECTED]> writes: > The one difference I can see between log-edit and status now is that > there are no <back-end>-log-edit functions that you can call by > yourself. I think a good solution would be to add it. That can be done > automatically from DVC's core, adding a wrapper function like > > (defun <back-end>-log-edit () > (interactive) > (let ((dvc-temp-current-active-dvc '<back-end>)) (dvc-log-edit))) > > Then, the normal flow would be to call M-x dvc-log-edit RET (or > keybinding), and users with specific needs can call M-x > <back-end>-log-edit RET explicitely. > > I can try to write a patch doing that ~tonight.
Just commited. So, you can now explicitely ask M-x xgit-log-edit RET if you want to commit in the git repository, even if it's not the default (i.e. not the most nested tree, or not the first in dvc-select-priority). It doesn't solve the problem of nested trees contained in each other using the same back-end, but I don't think DVC will ever support it, and at least _I_ will not implement it. Please, test the patch and let me know if it suits you. Then, you can fix your patch to only look for buffers managed by the current back-end, since you have an easy way to specify the back-end, so, no need for an additional prompt. -- Matthieu _______________________________________________ Dvc-dev mailing list [email protected] https://mail.gna.org/listinfo/dvc-dev
