all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, "T.V Raman" <raman@google.com>
Subject: Re: Prickliness of the "invalid byte code" stuff
Date: Fri, 21 Jun 2019 10:34:46 -0400	[thread overview]
Message-ID: <jwv5zoz3uqm.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83ef3npe85.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 21 Jun 2019 10:52:26 +0300")

> OK, thanks.  I did some more tests, and I think it's indeed OK to let
> this variable do nothing.

My original suggestion was just to declare it obsolete (and, as
a consequence, to stop using it in our own files).  So I just pushed that.

We can additionally change bytecomp to simply ignore the variable,
indeed, that's fine by me, but I think we can wait a bit before doing
that (even until Emacs-28, if you ask me).

> But I guess we still need to accept its specification in file-local
> variables without any errors, at least for some time?

Yes, of course.  Note that when compiling the file, any unknown
fie-local specifications are simply ignored, so if/when we remove the

    (put 'byte-compile-dynamic 'safe-local-variable 'booleanp)
    
it will not cause an error, but it will just prompt the user whether to
obey this "risky" setting instead of accepting it silently.


        Stefan




  parent reply	other threads:[~2019-06-21 14:34 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-15 12:36 Prickliness of the "invalid byte code" stuff Lars Ingebrigtsen
2019-06-15 14:30 ` Andreas Schwab
2019-06-16  2:40   ` Richard Stallman
2019-06-16 12:41     ` Lars Ingebrigtsen
2019-06-16 13:27       ` Stefan Monnier
2019-06-16 17:47     ` T.V Raman
2019-06-16 22:01       ` Stefan Monnier
2019-06-17  2:39         ` T.V Raman
2019-06-17 13:32           ` Stefan Monnier
2019-06-17 16:04             ` Richard Stallman
2019-06-17 18:10               ` Stefan Monnier
2019-06-17 22:52                 ` Paul Eggert
2019-06-17 22:53                   ` Stefan Monnier
2019-06-18  0:14                     ` T.V Raman
2019-06-18 12:14                       ` Stefan Monnier
2019-06-18 13:51                         ` T.V Raman
2019-06-18 14:15                           ` T.V Raman
2019-06-18 16:31                     ` Eli Zaretskii
2019-06-18 18:11                       ` Stefan Monnier
2019-06-18 18:23                         ` T.V Raman
2019-06-18 18:52                           ` Eli Zaretskii
2019-06-18 19:54                             ` T.V Raman
2019-06-19  2:36                               ` Eli Zaretskii
2019-06-19 13:54                                 ` T.V Raman
2019-06-19 15:36                                   ` Eli Zaretskii
2019-06-18 18:44                         ` Eli Zaretskii
2019-06-18 19:48                           ` Stefan Monnier
2019-06-18 19:52                             ` Stefan Monnier
2019-06-19 16:08                             ` Eli Zaretskii
2019-06-19 16:25                               ` Stefan Monnier
2019-06-19 17:04                                 ` Eli Zaretskii
2019-06-19 19:02                               ` Stefan Monnier
2019-06-19 21:35                                 ` T.V Raman
2019-06-21  7:52                                   ` Eli Zaretskii
2019-06-21 14:10                                     ` T.V Raman
2019-06-21 14:15                                       ` Eli Zaretskii
2019-06-21 14:34                                     ` Stefan Monnier [this message]
2019-06-21 15:04                                       ` Eli Zaretskii
2019-06-18  3:09                 ` Richard Stallman
2019-06-17 16:01           ` Richard Stallman

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=jwv5zoz3uqm.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=raman@google.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.