jfbu <[email protected]> writes: > 29 nov. 2014 at 09:45, David Kastrup wrote : > >>> >>> Makes me think that there could be a one-time-only >>> parsing of the .emacs and customization files when >>> a new Emacs major release is first executed by the >>> user, so as to signal possible mis-configuration. >> >> customize-changed-options is an interactive autoloaded Lisp function >> in `cus-edit.el'. >> >> It is bound to <menu-bar> <options> <customize> >> <customize-changed-options>. >> >> (customize-changed-options &optional SINCE-VERSION) >> >> Customize all settings whose meanings have changed in Emacs itself. >> This includes new user options and faces, and new customization >> groups, as well as older options and faces whose meanings or >> default values have changed since the previous major Emacs >> release. >> >> With argument SINCE-VERSION (a string), customize all settings >> that were added or redefined since that version. >> > > Thanks for the tip, > > M-x customize-changed-options > creates a giant customization buffer, I am not sure > what I am supposed to do with it. It just makes me realize > I know close to nothing to all modes provided with Emacs.
You probably want the intersection of M-x customize-saved RET with that. Perhaps with an addition of M-x customize-rogue RET as well... -- David Kastrup _______________________________________________ auctex mailing list [email protected] https://lists.gnu.org/mailman/listinfo/auctex
