From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Christopher Miles <numbchild@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, Dmitry Gutov <dgutov@yandex.ru>,
Stefan Kangas <stefan@marxist.se>, Leo Liu <sdl.web@gmail.com>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: Lift {global,local}-key-binding to Lisp
Date: Sun, 17 Jan 2021 16:10:59 +0000 [thread overview]
Message-ID: <87lfcrzgq4.fsf@tcd.ie> (raw)
In-Reply-To: <VI1PR1001MB1070C6A9D41E778347C9A040A3A50@VI1PR1001MB1070.EURPRD10.PROD.OUTLOOK.COM> (Christopher Miles's message of "Sun, 17 Jan 2021 14:33:05 +0000")
Christopher Miles <numbchild@gmail.com> writes:
> Leo Liu <sdl.web@gmail.com> writes:
>
>> On 2021-01-15 14:09 +0200, Dmitry Gutov wrote:
>>> Consider that, when a piece of code is implemented in Lisp, it's
>>> easier for us "mere mortals" to find it, read, understand and debug
>>> it. Even more so when it comes to people outside of emacs-devel.
>>
>> Eli is not against more elisp. In fact he encourages it.
>>
>> His principle is for C code that has been there for decades and is _not_
>> broken let us be cautious and make a clear case before moving it to
>> elisp.
>>
>> There could only be good things following this principle.
>
> If don't move this, then there is same reason to don't more others. Then don't
> change any C code which existed for a long time. So the result is don't touch
> any C code.... A reason like existing for decade time is not a reasonable
> argument. Should talking technically.
>
> An old house existing for decades, should not update it.... because it exists
> decades. We should talk about why update it. And Dmitry Gutov and Stefa gives
> clear reason. But you didn't give technical reason. So I think it's not really
> arguing correctly. Really should stop this.
You seem to have misunderstood - the argument isn't to never touch old C
code; it's to not touch it for superficial changes alone, for some
definition of superficial. Updating old code for necessary reasons is
always welcome.
--
Basil
prev parent reply other threads:[~2021-01-17 16:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 19:26 Lift {global,local}-key-binding to Lisp Eli Zaretskii
2021-01-14 19:24 ` Stefan Kangas
2021-01-14 20:10 ` Eli Zaretskii
2021-01-14 20:24 ` Eli Zaretskii
2021-01-15 1:58 ` Leo Liu
2021-01-15 4:16 ` Óscar Fuentes
2021-01-15 7:42 ` Eli Zaretskii
2021-01-21 16:03 ` Stefan Kangas
2021-01-21 16:59 ` [External] : " Drew Adams
2021-01-21 17:50 ` Dmitry Gutov
2021-01-21 18:16 ` Drew Adams
2021-01-21 18:58 ` Dmitry Gutov
2021-01-21 19:59 ` Eli Zaretskii
2021-01-14 21:03 ` Andrea Corallo via Emacs development discussions.
2021-01-15 7:45 ` Eli Zaretskii
2021-01-15 12:09 ` Dmitry Gutov
2021-01-15 12:18 ` Eli Zaretskii
2021-01-15 13:24 ` Dmitry Gutov
2021-01-15 13:45 ` Eli Zaretskii
2021-01-15 18:09 ` Dmitry Gutov
2021-01-17 14:27 ` Christopher Miles
2021-01-15 18:03 ` Drew Adams
2021-01-16 0:51 ` Leo Liu
2021-01-17 14:33 ` Christopher Miles
2021-01-17 15:08 ` Eli Zaretskii
2021-01-18 3:29 ` Christopher Miles
2021-01-18 16:43 ` Eli Zaretskii
2021-01-17 16:10 ` Basil L. Contovounesios [this message]
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=87lfcrzgq4.fsf@tcd.ie \
--to=contovob@tcd.ie \
--cc=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=numbchild@gmail.com \
--cc=sdl.web@gmail.com \
--cc=stefan@marxist.se \
/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).