From: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Why mouse-1/2/3 ?
Date: Mon, 27 Apr 2020 10:26:41 -0400 [thread overview]
Message-ID: <4865c7e7-129b-a509-694c-d4f037464e52@gmail.com> (raw)
In-Reply-To: <20200427140852.GA14552@tuxteam.de>
On 27/04/2020 10.08, tomas@tuxteam.de wrote:
> On Mon, Apr 27, 2020 at 09:36:41AM -0400, Clément Pit-Claudel wrote:
>> On 27/04/2020 07.31, tomas@tuxteam.de wrote:
>
> [...]
>
>>> If you want Emacs to adapt in this point, it's on you to convince
>>> Emacs people that this change is important.
>>
>> FWIW, I don't find the comparison to speaking German very convincing either.
>
> All metaphors suck in some way. My point is... I've seen all
> too often this antipattern: some enters an existing culture
> and shouts into the room "hey, why are you doing this in such
> a weird way? Come do it this other way I propose, it's much
> better!".
Sometimes it takes an outsider to point out that the emperor has no clothes.
Hopefully the Emacs culture is richer than our outdated terminology ^^
> I think if you want to convince people, you might want to go
> a bit smarter about that :-)
I'm not sure (besides, I'm not sure "smarter" is the right word here). Sometimes just asking "why" is enough to trigger interesting discussions. If we don't have a good answer to "why?" except "that how we've always done it", then maybe that's a sign that we're not doing it optimally. (for example, the other thread on Emacs looking square has yielded valuable new ideas).
next prev parent reply other threads:[~2020-04-27 14:26 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4865c7e7-129b-a509-694c-d4f037464e52@gmail.com \
--to=cpitclaudel@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.