From: "Phillip Lord" <phillip.lord@russet.org.uk>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>,
Jean-Christophe Helary <jean.christophe.helary@gmail.com>
Subject: RE: Major and minor modes
Date: Wed, 14 Jun 2017 07:37:41 -0000 [thread overview]
Message-ID: <0530dedd384a96dd99ba3a2c9d301cfa.squirrel@cloud103.planethippo.com> (raw)
In-Reply-To: <5202e0d6-4476-4e97-a5cb-f1ee66d562c3@default>
On Wed, June 14, 2017 1:49 am, Drew Adams wrote:
> 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.
I have thought for a long time that there are two forms of minor mode
which should be handled differently. Originally minor modes were clearly
meant to be global (auto-fill, line-number mode that sort of thing). But
there are lots of "single major mode" minor modes. Examples would be some
of the electric minor modes, things like Slime, CIDER or ensime which are
all minor modes more or less specific.
My own feeling is that minor modes have poor usability for these purposes.
Phil
next prev parent reply other threads:[~2017-06-14 7:37 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 [this message]
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=0530dedd384a96dd99ba3a2c9d301cfa.squirrel@cloud103.planethippo.com \
--to=phillip.lord@russet.org.uk \
--cc=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).