From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: xfq.free@gmail.com, simenheg@gmail.com, 21568@debbugs.gnu.org
Subject: bug#21568: [PATCH] Add prettify-symbols-alist for js-mode
Date: Sun, 27 Sep 2015 23:18:12 +0300 [thread overview]
Message-ID: <56084F04.2040501@yandex.ru> (raw)
In-Reply-To: <83y4frejbu.fsf@gnu.org>
On 09/27/2015 10:46 PM, Eli Zaretskii wrote:
> No, please leave that text alone. It's okay the way it is.
I feel that the last sentence causes unnecessary doubt on the part of
the reader. After all, CONTRIBUTE is intended as a guideline for
developing Emacs, and the less ambiguous it is, the better.
>> What I'm referring to is requests such as this one, which I believe
>> was/is misleading:
>>
>> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=21568#8
>
> I disagree that it was misleading.
It implied that without that cookie, something in that code might not
work well.
> Now that we have that text in CONTRIBUTE, that's all there is to say.
All right, thank you.
> I explained my reasons right there and then.
As a counterpoint, I don't believe educational purpose is a good enough
cause to ask people to use coding cookies in UTF-8 encoded Elisp files.
Even for external packages, over time, Emacs versions where they're
necessary will sail off into distant past. No need to add to the baggage
the future people will have to deal with.
> I really don't understand what this attack on me is about.
Please excuse any offense, but I'm not calling you names, or anything
like that.
I see an attempt to bring in extraneous practice into writing Elisp
files (as well as reviewing the patches), and speak against it.
next prev parent reply other threads:[~2015-09-27 20:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-26 11:49 bug#21568: [PATCH] Add prettify-symbols-alist for js-mode Simen Heggestøyl
2015-09-26 13:32 ` Eli Zaretskii
2015-09-26 15:59 ` Simen Heggestøyl
2015-09-27 0:39 ` Xue Fuqiao
2015-09-27 2:01 ` Dmitry Gutov
2015-09-27 6:04 ` Eli Zaretskii
2015-09-27 6:12 ` Dmitry Gutov
2015-09-27 7:28 ` Eli Zaretskii
2015-09-27 8:21 ` Dmitry Gutov
2015-09-27 8:39 ` Eli Zaretskii
2015-09-27 8:50 ` Dmitry Gutov
2015-09-27 10:03 ` Eli Zaretskii
2015-09-27 14:11 ` Dmitry Gutov
2015-09-27 18:37 ` Eli Zaretskii
2015-09-27 19:13 ` Dmitry Gutov
2015-09-27 19:46 ` Eli Zaretskii
2015-09-27 20:18 ` Dmitry Gutov [this message]
2015-09-27 21:01 ` Eli Zaretskii
2015-09-28 4:16 ` Explicit encoding cookie in Elisp files, was: " Dmitry Gutov
2015-09-28 7:27 ` Explicit encoding cookie in Elisp files " Eli Zaretskii
2015-09-28 7:53 ` Dmitry Gutov
2015-09-28 8:24 ` Eli Zaretskii
2015-09-28 22:54 ` Dmitry Gutov
2015-09-27 8:10 ` bug#21568: [PATCH] " Simen Heggestøyl
2015-09-27 14:28 ` Xue Fuqiao
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=56084F04.2040501@yandex.ru \
--to=dgutov@yandex.ru \
--cc=21568@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=simenheg@gmail.com \
--cc=xfq.free@gmail.com \
/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.