Rework init-file migration

Michael Sperber writes: The function name is too idiomatic for me, I didn't get it at first. Are you walking a tree here or something? Seriously, the nuance of "in order" is too forceful. It really is a user's choice. For example, Robert Chassell *likes* the "flexibility and clarity" of editing custom-set-* forms. (Professional driver on a closed course. Don't try this at home, kids.) Something like `user-init-file-migration-possible-p' might be better. I know this was discussed years ago, but I'd like to reopen it. Is this really a good idea? My impression is that people who really do run multiple Emacsen these days are either developers or are more likely to be running both the One True Editor and the GNU product. In both cases I think it makes more sense to pull out common code and load it explicitly from a version-specific init file. In the case of cross-branch sharing, AFAIK both Emacsen now support byte-compilation of the init file, which means sharing is right out due to incompatibility of the byte codes. You don't need "moreover" here. Makes you sound Shakespearean. :-) _______________________________________________ XEmacs-Patches mailing list XEmacs-Patches(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-patches