sb> You left out: sb> * Buffer name sb> * Coding System in effect sb> * Input Method State area sb> Maybe not the Input Method State as that is as modal as the sb> major/minor modes. Well, so is coding system, for that matter (besides not being particularly informative in the current incarnation). We certainly should do something about about all the real estate taken up by input method stuff. I don't find the information that I'm using Canna or whether it is currently active very useful. I'm normally looking at point or off-screen when I start trying to type English in Japanese henkan mode, not at the mode line. I think it would be a lot more useful to have the cursor change (shape, color, blink) to indicate state of the input method. Maybe a small button labeled with a character or three, as Windows input methods do. It could pop up an informative window about current state, or maybe even a dialog to set stuff. sb> Speaking of the mode-line, why do we need the `XEmacs:' string sb> in it? That is occasionally useful to me to distinguish between VW or W3, which have strongly customized behavior, and typical XEmacs semantics. But that's probably an abuse of the facility. I guess I would like a format like "MajorMode: Buffer name (minor modes)". (I think it's amusing that the longest mode tag in this window is "Abbrev" :-) -- 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 two straight lines for? "Free software rules."