Jan Vroonhof <vroonhof(a)math.ethz.ch> writes:
> 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.
I think it is a very weird feature for a first time user, however it
also very practical, and it doesn't get in the way. Now that we
start passing in the default value anyway for the history stuff, it
seems to be "cheap" to implement.
Do you think the two features could coexist? I don't see the point of
our DEFAULT parameter if FSF-style DEFAULT is one M-n away.
I haven't read the FSF manual, but I think that INITIAL-CONTENTS
vs
DEFAULT depends on the context. i.e. if you expect that the value
the user wants is "close" to the 'default', you should use
INITIAL-CONTENTS.
Yes. I.e. you use INITIAL-CONTENTS when you expect the user to edit
the contents. For instance, M-x w3-fetch provides a good example of
INITIAL-CONTENTS. M-x c-set-style provides a very bad example of
INITIAL-CONTENTS.