[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Emacs-diffs] /srv/bzr/emacs/trunk r105470: Improve documentation of
Re: [Emacs-diffs] /srv/bzr/emacs/trunk r105470: Improve documentation of `special' modes.
Wed, 17 Aug 2011 09:57:27 +0300
> From: Stefan Monnier <address@hidden>
> Cc: address@hidden
> Date: Tue, 16 Aug 2011 13:11:22 -0400
> > I don't actually have a good understanding of why would a mode want to
> > behave like that. The above explanation is purely phenomenological,
> > so if I would need to determine whether my mode needs it, I'd be
> > probably stumped. I don't really see the connection between
> > "specially-prepared" and "don't use me as the default mode".
> > Can you explain the considerations for when to use this feature? I
> > will then clarify this in the manual.
> Indeed, I'm just as lost as you are :-(
> For that reason, I'd be happy to get rid of this "use as the default
> mode" thingy. I.e. we should simply never inherit the major mode of new
> buffers from the current buffer (if the global value of major-mode is
> nil, then the default major-mode when creating a new buffer will be
> fundamental-mode, and that's it).
Are we sure the nil-means-use-current-buffer-major-mode feature is not
used too much to get rid of it?
And if we do that, how would a Lisp program specify that the major
mode of the current buffer is to be used for a newly created buffer?