all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Prickliness of the "invalid byte code" stuff
Date: Mon, 17 Jun 2019 12:04:23 -0400	[thread overview]
Message-ID: <E1hcu7L-0001BL-SF@fencepost.gnu.org> (raw)
In-Reply-To: <jwvo92wuyra.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Mon, 17 Jun 2019 09:32:17 -0400)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > > session. My thought was that if we  could detect this specific case,
  > > then we could as well have emacs load that file, rather than having the
  > > user reload it by hand.

  > Yes, that usually works, but unless we reorganize the current code, we
  > end up having to solve a slightly different problem similar to:

  >     (setq sm-foo (indirect-function '<pkg>-<fun>))
  >     (load "<pkg>")
  >     (funcall sm-foo <args>)

That is true -- but since indirect-function is called in only around
40 places, problems of this kind will be far less frequent than the
problems we have now.

And maybe we could fix some of those 40 places to avoid the problems,
in their own way.

We're talking about problems that result from an anomalous situation
in which we don't do the really right thing.  In such a case, a change
that reduces the frequency of problems can be a good thing, even if it
doesn'tmake things 100% correct.

The main criterion is that the change should never cause problems
in any non-anomalous situation.

-- 
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)





  reply	other threads:[~2019-06-17 16:04 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 [this message]
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
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=E1hcu7L-0001BL-SF@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.