unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thibaut Verron <thibaut.verron@gmail.com>
To: Robert Pluim <rpluim@gmail.com>
Cc: Daniele Nicolodi <daniele@grinta.net>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: CUA-theme?
Date: Thu, 17 Sep 2020 14:42:00 +0200	[thread overview]
Message-ID: <CAFsi02TLwD=nLOyYsjrnToxj_zY0BCdE0fWbtHyfpYVKw=YJsQ@mail.gmail.com> (raw)
In-Reply-To: <m2v9gc60y5.fsf@gmail.com>

>     Daniele> If I understand correctly the recent discussions, one of the main goals
>     Daniele> is to make Emacs more accessible to newcomers. In this respect, are we
>     Daniele> sure that using the "theme" concept, associated (outside the Emacs
>     Daniele> world) with customizing how applications looks, to configure the
>     Daniele> application behavior is a good idea?

I couldn't agree more.

>     Daniele> Reportedly, one of the things that newcomers struggle with is the
>     Daniele> peculiar and unique jargon used to describe Emacs concepts. This would
>     Daniele> add one more. I think the concept of "mode" as something that changes
>     Daniele> application behavior is well established and easier to explain.
>
> Except you then engender confusion with the Emacs concept of
> modes.

Only in the sense that it is more restrictive than the Emacs concept.
For example, cua-mode, delete-selection-mode and evil-mode are Emacs
modes and also application-behavior modes. I don't think there would
be a major confusion here, as by the time users see other modes, they
would be more used to Emacs terminology.

> Perhaps we should call them 'user type profiles' or something,
> then we could call them 'new-to-emacs-profile', 'vanilla-profile', etc.

That's also fine, but it might create confusion with user profiles,
which would typically cover *all* the settings, so that different
profiles would have different init files. That actually opens another
area for investigation: we could have Emacs support such user profiles
and have the configuration screen offer a choice for a "base profile"
(some kinds of factory settings).



  parent reply	other threads:[~2020-09-17 12:42 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         ` CUA-theme? Drew Adams
2020-09-17 12:42     ` Thibaut Verron [this message]
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='CAFsi02TLwD=nLOyYsjrnToxj_zY0BCdE0fWbtHyfpYVKw=YJsQ@mail.gmail.com' \
    --to=thibaut.verron@gmail.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).