Hi, I need to use xemacs 21.5 and 21.4 (beta and stable) depending on where I'm working. I keep a darcs repository (darcs is IMHO the best version control tool out there) of my .xemacs directory. I need to know if it's possible to do certain customizations differently for different versions of xemacs - is there a way of specifying a different custom.el file for different versions to use programatically via the init.el file, so that customize mode from different versions don't clash, for example? As a last resort, there has to be a variable or constant I can check that'll give me the current version of xemacs I'm using so I can base customizations on that. I realise I can just use different branches for different versions, and then synchronise shared patches between them (darcs makes that easy) but I'd prefer a more convenient way of doing it. Thanks

Glyn Millington writes: > Don't know how to do this with custom.el There are ways to choose which custom.el gets loaded at runtime, but I think it's a bad idea, since custom is basically opaque and version-blind. If you must, example code that shows how to deal with custom.el is in the sample init.el (available from the Help menu). > This might be another way .... > > (if (and (featurep 'mule) > (emacs-version>= 21 5 0)) This is what I would recommend. Note that code that might be shared with GNU Emacs can condition on (featurep 'xemacs). Another possibility would be to use the desktop package. While the use case hasn't been specified in detail, I suppose that there's a good chance that the usage of different versions would be spatially separated (ie, operating on files in different directories). If that's the case, then you could save the desktop file into the working directory, and start XEmacs from the same place. This isn't what desktop is designed for, exactly, but it should work. Also, I know that the OP is working on packages. If the issue is to use XEmacs 21.4 to compile packages, but he would prefer to use 21.5 to edit code, then -batch -vanilla doesn't read user customizations in any case. Thus setting XEMACS to point at xemacs-21.4 in the Local.rules file and always using make to compile libraries would do the trick.