Jan> That is because I happen to like the base structure of Jan> customize and because actually prefer using customize for the Jan> more non-trivial stuff such as reftex-label-alist I can see this. Customize is good at presenting a relatively convenient (within the interface constraints, which we have many ideas about improving already) interface to already orthogonal concepts. Eg, the components of individual faces for Latin fonts. Where it falls down big time is on things that aren't orthogonal. How many times have I wished I could get at things via the path property - widget - app instead of app - widget - property, and better yet find that Custom had defaulted the app and the widget sensibly from context? (Sure, if the Customizers are careful about constructing a multi-rooted DAG rather than a tree, you _can_ do that, and this is often the case. It often is not, though, and Custom should be able to compute these relationships. In theory, anyway....) Or Japanese doesn't use bold, italic, or underline, but has its own analogs. These analogs can't be chosen directly through Custom, even in principle, but have to be encoded in font family choice. And in some cases aren't available at all (those would be very hard to implement, though). This is _not_ the "Custom don't grok outside of ISO-Latin problem". Rather, Custom doesn't understand that idea that "in some specifier locales these properties are important, but elsewhere those are instead." And on grouping related things as the _user_ sees them. Most people don't care about Japanese emphasis, and they shouldn't have to. But I would like Custom to provide a _user_-level interface that allows me to create arbitrary mappings of real properties to "virtual" properties, preferably based on specifiers, so that I can get rid of the "italic" property that I don't really care about and replace it with an "ordinary emphasis" property that I do care about. (OK, this probably can't be "user" level, since users often don't understand "virtual" or "mapping" very well. But it could be more convenient for sophisticated users in simple things.) I don't think "themes" is the answer to this issue, themes provide a sensible framework for defaulting things that Custom already does well on a case-by-case basis. One interface thing that often chafes me in the Custom interface is that I would often like to reorder lists (eg, when an alist's elements aren't orthogonal, so its order matters). Is there an easy way to do this? At present I use a sexp widget to contain the whole list when convenience in selection and kill/yank operations is important, rather than a list widget with its INS/DEL interface. -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."