all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Explicit encoding cookie in Elisp files Add prettify-symbols-alist for js-mode
Date: Tue, 29 Sep 2015 01:54:19 +0300	[thread overview]
Message-ID: <5609C51B.3050706@yandex.ru> (raw)
In-Reply-To: <83k2rbdk8u.fsf@gnu.org>

On 09/28/2015 11:24 AM, Eli Zaretskii wrote:

> Of course.  But I still routinely work on systems where 23.2 is the
> latest installed version, and I'm a simple user there, so I cannot
> upgrade that.

Hopefully, you don't have to work on Emacs too much in those conditions.

> I did what I did semi-automatically because we were doing that for
> years.  I didn't even remember that we default to UTF-8 in *.el files
> until Stefan reminded me.  Why? because we never bothered to remove
> the cookies after we made that change, nor stop producing them in
> auto-generated *.el files.

Cookies still make sense in loaddefs, because those are created inside 
.emacs.d/elpa as well.

> Inconsistency?  Yes, I dislike it, but I dislike discrimination and
> lack of fair play even more.

Ok, I've removed most of those old occurrences too, so that the tiny new 
commit doesn't feel too discriminated against. Hopefully, it won't cause 
significant difficulties on your systems with Emacs 23.2.

I didn't touch Org, Gnus, CC Mode, Tramp and loaddefs files. As well as 
the directories leim, language and international, because those are 
terrifying.

> Once again, you are blowing out of proportion a minor issue.  It lacks
> any potential for any kind of grave consequences, so far-fetched

Analogies sometimes get exaggerated for clarity.

Note that "desugaring" in the presented analogy doesn't have any "grave 
consequences" either. It's a pretty safe operation, all in all.

> Judging by the energy invested in this discussion, I don't think we
> should lack manpower/enthusiasm to fix the issue consistently, only
> redirect it.  Assuming, that is, that the issue is indeed the cookies
> themselves.

My issue was with the proposed change in the workflow for new 
contributions. But I hope you're okay with the result.

> Then why did you want to revert db828f6?

It seems to be a fitting conclusion for this discussion, that's all.



  reply	other threads:[~2015-09-28 22:54 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
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 [this message]
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=5609C51B.3050706@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=eliz@gnu.org \
    --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.