From: Drew Adams <drew.adams@oracle.com>
To: Jean-Christophe Helary <jean.christophe.helary@gmail.com>,
Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>
Subject: RE: Major and minor modes
Date: Tue, 13 Jun 2017 18:49:14 -0700 (PDT) [thread overview]
Message-ID: <5202e0d6-4476-4e97-a5cb-f1ee66d562c3@default> (raw)
In-Reply-To: <AB12E834-02F6-4437-9215-7F714C3C2955@gmail.com>
> > Can anyone explain to me clearly how Major modes and minor modes work
> together. Can any minor mode work within any major mode? How do these work
> together?
>
> Everything is explained in Chapter 20 of the Emacs Manual.
Depends what Emacs version you use. For versions 24 and 25
it is chapter 23, "Major and Minor Modes". For version 23
it is chapter 27, "Major Modes" and section and 57.1, "Minor
Modes". It is here:
http://www.gnu.org/software/emacs/manual/html_node/emacs/Modes.html
In sum, a major mode is buffer-specific.
As such, it typically does something appropriate for that
buffer content.
A minor mode can be buffer-specific (local) or not (global).
Minor-mode key bindings override major-mode key bindings.
A minor mode can do anything at all. What it does need not
be specific for the content of any particular buffer, and
hence for any particular major mode.
next prev parent reply other threads:[~2017-06-14 1:49 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 23:58 Major and minor modes M.R.P.
2017-06-14 0:43 ` Jean-Christophe Helary
2017-06-14 1:49 ` Drew Adams [this message]
2017-06-14 3:49 ` Jean-Christophe Helary
2017-06-14 3:59 ` Emanuel Berg
2017-06-15 4:58 ` Marcin Borkowski
2017-06-14 14:23 ` Eli Zaretskii
2017-06-14 21:58 ` Jean-Christophe Helary
2017-06-14 23:10 ` Jean-Christophe Helary
2017-06-15 13:33 ` Emanuel Berg
2017-06-15 15:05 ` Eli Zaretskii
2017-06-15 15:16 ` Drew Adams
2017-06-16 2:09 ` Jean-Christophe Helary
2017-06-16 3:07 ` Drew Adams
2017-06-16 4:44 ` Emanuel Berg
2017-06-16 5:13 ` Jean-Christophe Helary
2017-06-16 5:26 ` Emanuel Berg
2017-06-16 6:59 ` Eli Zaretskii
2017-06-16 8:02 ` Jean-Christophe Helary
2017-06-16 4:34 ` Emanuel Berg
2017-06-14 4:05 ` Emanuel Berg
2017-06-17 14:08 ` Narendra Joshi
2017-06-19 4:43 ` Krishnakant
2017-06-14 6:21 ` Krishnakant
2017-06-14 7:37 ` Phillip Lord
2017-06-14 1:54 ` Emanuel Berg
2017-06-14 7:40 ` Héctor Lahoz
2017-06-14 8:19 ` Emanuel Berg
2017-06-14 8:51 ` tomas
2017-06-14 9:25 ` Emanuel Berg
2017-06-14 9:36 ` Emanuel Berg
2017-06-14 9:58 ` tomas
2017-06-14 10:43 ` Emanuel Berg
2017-06-14 11:39 ` Emanuel Berg
2017-06-14 11:48 ` Emanuel Berg
2017-06-14 12:19 ` tomas
2017-06-14 14:15 ` Barry Margolin
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=5202e0d6-4476-4e97-a5cb-f1ee66d562c3@default \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=jean.christophe.helary@gmail.com \
/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.
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).