unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] /srv/bzr/emacs/trunk r105470: Improve documentation of `special' modes.
Date: Tue, 16 Aug 2011 13:11:22 -0400	[thread overview]
Message-ID: <jwvbovpwajd.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <838vqttoaf.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 16 Aug 2011 17:38:00 +0300")

>> > +If this mode is appropriate only for specially-prepared text produced by
>> > +the mode itself (rather than by the user typing at the keyboard or by an
>> > +external file), then the major mode command symbol should have a
>> > +property named @code{mode-class} with value @code{special}, put on as
>> > +follows:
>> AFAIK we also use `special' for things like doc-view-mode.
> It was mostly the old text, I just added the part in parentheses.
> 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).


        Stefan



       reply	other threads:[~2011-08-16 17:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1QtFlp-0000bn-JP@vcs.savannah.gnu.org>
     [not found] ` <jwvk4adxx0u.fsf-monnier+emacs@gnu.org>
     [not found]   ` <838vqttoaf.fsf@gnu.org>
2011-08-16 17:11     ` Stefan Monnier [this message]
2011-08-17  6:57       ` [Emacs-diffs] /srv/bzr/emacs/trunk r105470: Improve documentation of `special' modes Eli Zaretskii
2011-08-17 14:02         ` Stefan Monnier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvbovpwajd.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).