From: Emanuel Berg <moasen@zoho.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Major and minor modes
Date: Wed, 14 Jun 2017 03:54:53 +0200 [thread overview]
Message-ID: <86k24f5o5u.fsf@zoho.com> (raw)
In-Reply-To: z-SdnaV-lJGz4d3EnZ2dnUU7-cHNnZ2d@giganews.com
M.R.P. wrote:
> Can anyone explain to me clearly how Major
> modes and minor modes work together. Can any
> minor mode work within any major mode?
In general, the major mode is the big frame
and there is one and only one major mode to
help you edit the text in the buffer. So for C,
it is C/l defined in cc-mode.el, and so on.
The minor mode is a small piece of
functionality, like Line-Number to have the
current line shown in the mode bar. It is
a good thing it can be used in all but whatever
major mode so it doesn't have to be duplicated.
In principle I suppose you can have as many
minor modes as you want for any major mode but
it isn't difficult to predict a scenario where
the minor modes contradict each other and/or
work in opposite ways to what makes sense for
the underlying major mode.
I never heard of anyone putting up fences in
their code to prevent that, and it is a good
thing they didn't as that would make all code
interdependent and besides people aren't that
stupid to setup a system that doesn't make
sense anyway. And if they are, let's go
nuts already.
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2017-06-14 1:54 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
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 [this message]
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=86k24f5o5u.fsf@zoho.com \
--to=moasen@zoho.com \
--cc=help-gnu-emacs@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.
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).