unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Richard Stallman <rms@gnu.org>
Cc: eliz@gnu.org, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] master 19e09cf: Ensure redisplay after evaluation
Date: Mon, 09 Nov 2015 20:16:12 -0500	[thread overview]
Message-ID: <jwv37weirlw.fsf-monnier+emacsdiffs@gnu.org> (raw)
In-Reply-To: <E1ZvuIT-0001IN-3E@fencepost.gnu.org> (Richard Stallman's message of "Mon, 09 Nov 2015 16:48:17 -0500")

>> I fully agree with Richard that it's a facility with which you can shoot
>> yourself in the foot in many different ways, 

> It's worse that that; what I said is stronger than that.
> If you write private code that creates advice, at worst you shoot
> yourself in the foot.  But if you insert code to create advice into
> the code of Emacs, you shoot anyone else that needs to debug cases
> where that advice has an effect.

You lost me here.  What I'm suggesting is to add a hook that's called
when some variables are modified.  So to me it sounds just like advice: as
long as you don't use this hook, Emacs's behavior is unchanged.
And just like with an advice, if you use such a hook in your ~/.emacs
you can shoot yourself in the foot, but if you use this is one of your
package, you might shoot the foot of your users.


        Stefan



  reply	other threads:[~2015-11-10  1:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20151106192313.30794.29154@vcs.savannah.gnu.org>
     [not found] ` <E1ZumbR-00081I-Hj@vcs.savannah.gnu.org>
2015-11-07 23:40   ` [Emacs-diffs] master 19e09cf: Ensure redisplay after evaluation Stefan Monnier
2015-11-08 16:12     ` Eli Zaretskii
2015-11-08 22:24       ` Stefan Monnier
2015-11-09 21:48         ` Richard Stallman
2015-11-10  1:16           ` Stefan Monnier [this message]
2015-11-10 18:18             ` Richard Stallman
2015-11-10 19:34               ` Stefan Monnier
2015-11-09 19:06       ` John Wiegley
2015-11-09 19:17         ` Eli Zaretskii
2015-11-09 21:57           ` John Wiegley
2015-11-13  0:31           ` Noam Postavsky
2015-11-13  8:06             ` Eli Zaretskii
2015-11-13 13:58               ` Stefan Monnier
2015-11-13 16:36               ` Noam Postavsky
2015-11-13 18:47                 ` Eli Zaretskii

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=jwv37weirlw.fsf-monnier+emacsdiffs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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 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).