unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] master 28b7dd4 2/2: Fix build error in bytecomp.el from previous change
Date: Tue, 01 Oct 2019 17:22:09 +0200	[thread overview]
Message-ID: <87tv8s32zi.fsf@gnus.org> (raw)
In-Reply-To: <jwva7akzete.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 01 Oct 2019 11:08:31 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> -(eval-when-compile (require 'compile))
>> +(require 'compile)
>
> This is a bad change.
>
> It brings in many more packages, and every additional package brought
> in reduces the quality of our warnings (e.g. if any of the packages
> (transitively) loaded load cl-lib, then we fail to signal when
> a package uses cl-lib functionality without requiring cl-lib).

I'm not quite sure I followed the last bit -- if something transitively
required cl-lib, then there's no point for the "top" file to require
cl-lib, surely?  Or is this a style issue.

But I agree that requiring compile.el runtime is probably not good, but:

> We should try and find some other solution.

No other solution I thought of at the top of my head seemed good.
Moving either of those keymaps to a different place seemed logical,
either...

The problem is that the mode now inherits from the parent defined in
compile.el:

(defvar emacs-lisp-compilation-mode-map
  (let ((map (make-sparse-keymap)))
    (set-keymap-parent map compilation-minor-mode-map)
    (define-key map "g" 'emacs-lisp-compilation-recompile)
    map))

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no



  reply	other threads:[~2019-10-01 15:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191001144135.32717.19241@vcs0.savannah.gnu.org>
     [not found] ` <20191001144137.1032C20927@vcs0.savannah.gnu.org>
2019-10-01 15:08   ` [Emacs-diffs] master 28b7dd4 2/2: Fix build error in bytecomp.el from previous change Stefan Monnier
2019-10-01 15:22     ` Lars Ingebrigtsen [this message]
2019-10-01 21:30       ` Stefan Monnier
2019-10-03 15:18         ` Lars Ingebrigtsen
2019-10-02 16:57     ` Sven Joachim

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=87tv8s32zi.fsf@gnus.org \
    --to=larsi@gnus.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 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).