[SOLVED for GNU] (was: (vc-annotate-revision-previous-to-line) rcs, cannot go back)

Uwe Brauer writes: Of course. I think the last major sync was done in 2005 or so by Ville Skyttä. The problem is that there are few workers to do it, and most of us seem to give other plans higher priority. Note that Stefan Monnier thinks that GNU's vc.el needs a thorough overhaul. I don't see anything hacky about using rlog. It is the obvious way to get the information. Your requirements are hacky, in the sense that the previous revision computed here is typically not the parent of the first revision on a branch. ("Typically" for all users. I'm not saying this won't work fine for you, but you should be aware of the gotcha.) This implementation assumes that once you branch, you close the old branch to further development: trunk 1.1 -- 1.2 -- 1.3 -- 1.4 \ branch 1 2.1 -- 2.2 \ branch 2 3.1 -- 3.2 -- ... But it would fail to pick out parents if development could continue: trunk 1.1 -- 1.2 -- 1.3 -- 1.4 -- 1.5 -- ... \ branch 1 2.1 -- 2.2 -- 2.3 -- ... \ branch 2 3.1 -- 3.2 -- ... This looks incorrect, if 1.y is your trunk, and x.y for x > 1 are branches. In that case you should change the regexp to "\\`1\\.[0-9]+\\'". This is false for CVS.[1] x.y (almost always 1.y) is a trunk version, branch versions have an even number of components greater than 2. RCS doesn't encourage such a convention as far as I can tell. There's nothing in the implementation you posted that wouldn't work in XEmacs AFAICS. I suspect that XEmacs vc just doesn't find the new function. Try naming the function "vc-rcs-previous-version" instead and see if XEmacs calls it properly. Footnotes: [1] I am so glad I work on XEmacs where we at least occasionally care about getting this kind of thing right.... _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta