Stephen Leake, 2007-04-28: > Those are usefull commands; xmtn-revlist-diff-to-current-tree does > give the preview I want.
Ok, great. > But my problem is how to let the user know those commands are there, > and how to make it easier to invoke them. > > Right now, the only way to find out about them is to read the lisp > source, and the only way to invoke them is M-x. You're right, it's neither easily discoverable nor easy to use. And that's undesirable, because it's a fairly important operation (which is why I implemented it). By the way, another useful command in this context is `xmtn-revlist-missing-revisions' on a head revision. It shows you the revisions that are ancestors of the selected revision, but not of your workspace base revision. The diff you originally asked for is (assuming no divergence) the combined diff of all these revisions; with this command, you can see the individual diffs and changelog messages. > A user manual would be nice, but most people don't bother reading > them. > > Menus are how most people learn about new user interfaces like DVC. > Well, in the absense of one-on-one mentoring, anyway. > > Menus and corresponding keystrokes are also an easy way to invoke > these commands. I haven't investigated yet how to add xmtn backend-specific key bindings or menus to DVC, and I don't think I will in the near future. They would be good to have, but I prefer working on the infrastructure right now. Feel free to add what you need. Christian. _______________________________________________ Dvc-dev mailing list [email protected] https://mail.gna.org/listinfo/dvc-dev
