xmtn-dvc-missing checks to see how many heads there are, and aborts if there are more than one.
However, if I comment out that check, I think the resulting display shows the multiple heads quite clearly. Although I'd like to invert the order, so most recent is at the top of the buffer; that's how 'mtn log' displays. So I don't understand why that check is there. Perhaps xmtn-dvc-missing could just issue a warning message to draw attention to the multiple heads. There is a comment about prompting the user to choose a head. I guess if there are 10 revisions leading to one head, and 20 leading to another, you might want to focus only on one head. That hasn't happened to me yet; does it happen often? Perhaps a ^-u option to cause xmtn-dvc-missing to prompt for a head would be good. Or maybe a ^-u option to bypass the check. Since there is no 'dvc-heads' command, I'm not clear what the user is supposed to do in response to the "more than one head" error message. There is xmtn-view-heads-revlist, which shows just the heads. So perhaps there could be a dvc-heads command, if other back-ends support such a thing. But I prefer the dvc-missing command without the check, since it shows the revisions leading up to the heads as well. dvc-missing is more tolerable with the last-n option in force; I have it set to 10. Although for the monotone main branch, 10 isn't high enough; it's a very active project, so there tend to be more revisions between the times I sync. So I think we need a way to set DVC options on a per-project basis. Something like a .dvcrc file in the root directory? I guess I can get the same effect with some lisp code on dvc-status-mode-hook; I'll try that first. But dvc-log-last-n needs to be buffer-local; I'll try that. -- -- Stephe _______________________________________________ Dvc-dev mailing list [email protected] https://mail.gna.org/listinfo/dvc-dev
