From: Drew Adams <drew.adams@oracle.com>
To: Robert Pluim <rpluim@gmail.com>, Daniele Nicolodi <daniele@grinta.net>
Cc: emacs-devel@gnu.org
Subject: RE: CUA-theme?
Date: Thu, 17 Sep 2020 16:14:20 +0000 (UTC) [thread overview]
Message-ID: <786ac18f-d614-4b04-b6cb-8a093b6cd6c4@default> (raw)
In-Reply-To: <m2r1r05zea.fsf@gmail.com>
>> Why do you think there would be confusion with the Emacs concept of
>> mode? Aren't Emacs modes things that change how Emacs behaves and
>> defines keybindings?
>
> Because an emacs mode is "hereʼs some specific functionality for this
> type of editing/code/etc", and this other mode is "hereʼs a collection
> of parameters and Emacs modes configured in such a way that itʼs
> easier for people coming from non-Emacs editors".
Major modes, maybe. But not minor modes. Not in general.
A mode is just an interactive context that provides
a particular experience. It encapsulates behavior, and
you can turn it on and off.
Both things you describe can be usefully handled as modes:
(1) specific functionality for a given type of activity,
and (2) a collection of settings and contexts (possibly
via modes) for some particular experience.
next prev parent reply other threads:[~2020-09-17 16:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 13:29 CUA-theme? Stefan Monnier
2020-09-16 14:29 ` CUA-theme? Tim Van den Langenbergh
2020-09-16 17:22 ` CUA-theme? Stefan Monnier
2020-09-16 20:19 ` CUA-theme? Juri Linkov
2020-09-17 11:08 ` CUA-theme? Daniele Nicolodi
2020-09-17 12:29 ` CUA-theme? Robert Pluim
2020-09-17 12:35 ` CUA-theme? Daniele Nicolodi
2020-09-17 13:03 ` CUA-theme? Robert Pluim
2020-09-17 16:14 ` Drew Adams [this message]
2020-09-17 12:42 ` CUA-theme? Thibaut Verron
2020-09-17 13:33 ` CUA-theme? Stefan Monnier
2020-09-17 14:01 ` CUA-theme? Arthur Miller
2020-09-17 14:13 ` CUA-theme? 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=786ac18f-d614-4b04-b6cb-8a093b6cd6c4@default \
--to=drew.adams@oracle.com \
--cc=daniele@grinta.net \
--cc=emacs-devel@gnu.org \
--cc=rpluim@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.
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).