Yoshiki Hayashi <t90553(a)m.ecc.u-tokyo.ac.jp&gt; writes: XEmacs does not support DEFAULT. FSF's DEFAULT causes M-n to insert the default contents, making it look like it's a first item in the "future" of the history list. It does not affect what happens when you just press RET. The DEFAULT argument you added does something different -- it affects what happens when you just press RET, and it stores the correct thing to history. It works nicely with the traditional "Insert something (default foo): " Emacs prompts. FSF's DEFAULT has the advantage that you can edit the default, and change it. If we had DEFAULT implemented, I would also recommend it over INITIAL-CONTENTS. I'm not sure whether we want it implemented. The M-n feature looks very weird to me. What do /you/ think? As a side note, maybe we should call our DEFAULT argument differently, to avoid horrible confusion with FSF's DEFAULT. Feel free to document it in minibuf.texi. read-passwd is in xemacs-base. XEmacs is not really meant to be used without xemacs-base. I don't think it's intentional. But please beware adding DEFAULT arguments because of the different user interface from the FSF. Be very careful of what you're doing here. If we make a wrong step, we could regret it later.