unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: <tomas@tuxteam.de>
To: emacs-devel@gnu.org
Subject: Re: Why mouse-1/2/3 ?
Date: Mon, 27 Apr 2020 13:31:41 +0200	[thread overview]
Message-ID: <20200427113141.GH30150@tuxteam.de> (raw)
In-Reply-To: <NaXFBqRrEd4QgzeTCphUuZ6mvfyq-fdoqevPjAskkn1q4qbCKUgafL3Ib30sT3SRKWRM5pElIiky9dB3xV-uLxhIvu2ObpvovgzC9L8iGDc=@protonmail.com>

[-- Attachment #1: Type: text/plain, Size: 803 bytes --]

On Mon, Apr 27, 2020 at 11:23:47AM +0000, ndame wrote:
> > Like a friend of mine said the other day: "why do the people have to speak
> > constantly English and don't speak German, as everyone else does?" :-)
> 
> Yep. It's like saying Emacs doesn't need to adapt, if someone wants to use it
> then learn the emacs terminology.

If you want Emacs to adapt in this point, it's on you to convince Emacs people
that this change is important.

You haven't managed to convince me, at least (I'm not an important "Emacs
people", just a happy user, mind you). Mentioning the alternative spellings
in the documentation and in the help, yes, by all means. But changing the
names in the code... not for me, at least.

There are far more important usability tasks, in my view.

Cheers
-- tomás

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2020-04-27 11:31 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-27 11:23 Why mouse-1/2/3 ? ndame
2020-04-27 11:31 ` tomas [this message]
2020-04-27 13:36   ` Clément Pit-Claudel
2020-04-27 13:39     ` Dmitry Gutov
2020-04-27 14:08     ` tomas
2020-04-27 14:26       ` Clément Pit-Claudel
2020-04-27 14:50         ` tomas
2020-04-27 16:00     ` Drew Adams
2020-04-27 19:04       ` chad
2020-04-28  2:51         ` Richard Stallman
2020-04-28  3:48           ` Tim Cross
2020-04-27 16:01     ` Drew Adams
  -- strict thread matches above, loose matches on Subject: below --
2020-04-27 10:50 ndame
2020-04-27 10:37 ndame
2020-04-27 10:40 ` tomas
2020-04-27 12:32   ` Ulrich Mueller
2020-04-28  2:47     ` Richard Stallman
2020-04-27 10:41 ` Andreas Schwab
2020-04-27 10:47   ` ndame
2020-04-27 11:02     ` tomas
2020-04-27 10:53   ` ndame
2020-04-27 11:11 ` Po Lu
2020-04-27 13:29   ` Clément Pit-Claudel
2020-04-27 13:14 ` Dmitry Gutov
2020-04-27 13:27   ` ndame
2020-04-27 15:08     ` Dmitry Gutov
2020-04-25 17:45 ndame
2020-04-25 18:19 ` Zach Pearson
2020-04-26  4:09   ` Po Lu
2020-04-27  9:45     ` ndame
2020-04-27  9:53       ` tomas
2020-04-27 11:10       ` Po Lu
2020-04-27 11:12         ` ndame
2020-04-27 11:46           ` Po Lu
2020-04-26  4:08 ` Po Lu
2020-04-26  6:12   ` Tim Cross
2020-04-26 16:41   ` Drew Adams
2020-04-27  9:30     ` Po Lu
2020-04-27  9:40       ` tomas
2020-04-27  9:47         ` Pip Cet
2020-04-27 15:13           ` Stefan Monnier
2020-04-28  0:40 ` Michael Welsh Duggan
2020-04-28 15:27   ` Drew Adams

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=20200427113141.GH30150@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=emacs-devel@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.
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).