The XEmacs (and Emacs in general) user interface is pretty different from what is expected of a typical MS Windows program. How does the MS Windows port cope with it?
As a general rule, we follow native MS Windows conventions as much as possible. 21.4 is a fairly complete Windows application, supporting native printing, system file dialog boxes, tool tips, etc. In cases where there’s a clear UI conflict, we currently use normal Unix XEmacs behavior by default, but make sure the MS Windows “look and feel” (mark via shift-arrow, self-inserting deletes region, Alt selects menu items, etc.) is easily configurable (respectively: using the variable shifted-motion-keys-select-region in 21.4 and above [it’s in fact the default in these versions], or the `pc-select’ package; using the `pending-del’ package; and setting the variable menu-accelerator-enabled to menu-force in 21.4 and above). In fact, if you use the sample `init.el’ file as your init file, you will get all these behaviors automatically turned on. In future versions, some of these features might be turned on by default in the MS Windows environment.
Related Questions
- The XEmacs (and Emacs in general) user interface is pretty different from what is expected of a typical MS Windows program. How does the MS Windows port cope with it?
- XEmacs (and Emacs in general) UI is pretty different from what is expected of a typical MS Windows program. How will the MS Windows port cope with it?
- Is Smart Energy having a user friendly interface for zone input? If yes then in what it is different from existing?