unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Arthur Miller <arthur.miller@live.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Daniele Nicolodi <daniele@grinta.net>, emacs-devel@gnu.org
Subject: Re: CUA-theme?
Date: Thu, 17 Sep 2020 16:01:25 +0200	[thread overview]
Message-ID: <VI1PR06MB45268F2065F11DDEFF21EE3D963E0@VI1PR06MB4526.eurprd06.prod.outlook.com> (raw)
In-Reply-To: <jwvy2l8mt2q.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 17 Sep 2020 09:33:29 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> Daniele Nicolodi [2020-09-17 13:08:50] wrote:
>
>> On 16/09/2020 15:29, Stefan Monnier wrote:
>>> Would it make sense to define a new custom-theme (or minor-mode until
>>> custom-theme can handle that) which makes Emacs's behavior match the
>>> "standard" in most other applications?
>>
>> If I understand correctly the recent discussions, one of the main goals
>> is to make Emacs more accessible to newcomers. In this respect, are we
>> sure that using the "theme" concept, associated (outside the Emacs
>> world) with customizing how applications looks, to configure the
>> application behavior is a good idea?
>
> I'm not interested in the user-facing part where we decide what name to
> show to the users (where we likely won't give it a name at all, instead
> we'll just have a button saying "follow non-Emacs standards").
> I'm talking about the underlying technique.

If it not interesting to expose to a user how the thing is implemented,
then you can as well have it as a mode and not introduce yet another
thing Emacs does differently.

> It's easy to take a theme and then add further changes on top of it
> (some of which may "undo" changes made by the theme) and it is supposed
> to work reliably.  Whereas enabling/disabling a minor mode which enables
> `delete-selection-mode` (for example) will often misbehave in corner
> cases when mixed in with enabling/disabling `delete-selection-mode`.
Then it sounds like a bug somewhere and should probably be fixed?



  reply	other threads:[~2020-09-17 14:01 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     ` CUA-theme? Thibaut Verron
2020-09-17 13:33   ` CUA-theme? Stefan Monnier
2020-09-17 14:01     ` Arthur Miller [this message]
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=VI1PR06MB45268F2065F11DDEFF21EE3D963E0@VI1PR06MB4526.eurprd06.prod.outlook.com \
    --to=arthur.miller@live.com \
    --cc=daniele@grinta.net \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).