unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Deny keymap changes made by `evil-integration'
Date: Sat, 25 Jul 2015 16:20:39 +0300	[thread overview]
Message-ID: <83io981ihk.fsf@gnu.org> (raw)
In-Reply-To: <CAKu-7WytCAwf+jvoXhmxjtBLO50ZAnfUd3wggcs6SQTQPpU1ZQ@mail.gmail.com>

> Date: Sat, 25 Jul 2015 14:52:43 +0200
> From: Alexander Shukaev <haroogan@gmail.com>
> Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
> 
> They implemented `evil' too intrusively, i.e. `(require 'evil)' would
> also `(require 'evil-integration)' and some other trash that I don't
> want personally.

I'd suggest a careful reading of the code, looking for ways of
disabling the too-intrusive stuff.

> Do you propose
> 
> (with-eval-after-load 'evil
>    (with-evail-after-load 'dired
>      (load "dired"))
> 
>    (with-evail-after-load 'whatever
>      (load "whatever"))
> 
>    ...)
> 
> ?

Something like that, yes.

> Still I have 2 problems with this.  First of all, shouldn't there
> be an infinite recursion here (with-eval-after-load/load combo)?
> Secondly, `evil-integration' wraps it's configurations for `dired'
> also with `eval-after-load'; doesn't this mean that reloading `dired'
> will not change anything because the wrapped snippet (from
> `evil-integration') will execute again?

Nothing that (let (after-load-alist) (load "...")) couldn't solve.



  reply	other threads:[~2015-07-25 13:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-25 11:43 Deny keymap changes made by `evil-integration' Alexander Shukaev
2015-07-25 11:47 ` Eli Zaretskii
2015-07-25 11:58   ` Alexander Shukaev
2015-07-25 12:33     ` Eli Zaretskii
2015-07-25 12:52       ` Alexander Shukaev
2015-07-25 13:20         ` Eli Zaretskii [this message]
2015-07-25 13:23           ` Alexander Shukaev
2015-07-27 21:09             ` John Mastro
2015-07-28 13:28               ` Alexander Shukaev
2015-07-26 12:24           ` Martin Yrjölä
2015-07-26 18:56             ` Alexander Shukaev
2015-07-27 20:46 ` Robert Thorpe

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=83io981ihk.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@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.
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).