From: Christopher Miles <numbchild@gmail.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Eli Zaretskii <eliz@gnu.org>,
"stefan@marxist.se" <stefan@marxist.se>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: Lift {global,local}-key-binding to Lisp
Date: Sun, 17 Jan 2021 14:27:37 +0000 [thread overview]
Message-ID: <VI1PR1001MB107077A77F3A29E6D27E78C6A3A50@VI1PR1001MB1070.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <35d8da3e-7761-bbf2-4890-543fc6f0f52f@yandex.ru>
[-- Attachment #1: Type: text/plain, Size: 1043 bytes --]
Dmitry Gutov <dgutov@yandex.ru> writes:
> On 15.01.2021 15:45, Eli Zaretskii wrote:
>>>> Once again, we need to address this on a case by case basis; an
>>>> abstract principle will fail to lead to wise, balanced decisions.
>>> We need to have some guidelines, though, in order to avoid arguing about
>>> every such commit.
>> I've already posted them, just a few messages back.
>
> As long as you're aware that "code cleanups" (that don't add much in the
> way of functionality) are often a good way for new developers to
> familiarize themselves with the codebase.
I agree with Gutov's opinion, I'm one of new developer who is more familiar with
Lisp instead of C. When I [M-.] to a C source file. I close it immediately. Not
complex reason, just can't read them.
--
[ stardiviner ]
I try to make every word tell the meaning that I want to express.
Blog: https://stardiviner.github.io/
IRC(freenode): stardiviner, Matrix: stardiviner
GPG: F09F650D7D674819892591401B5DF1C95AE89AC3
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-01-17 14:27 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 [this message]
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
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=VI1PR1001MB107077A77F3A29E6D27E78C6A3A50@VI1PR1001MB1070.EURPRD10.PROD.OUTLOOK.COM \
--to=numbchild@gmail.com \
--cc=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--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).