From: Eli Zaretskii <eliz@gnu.org>
To: John Wiegley <jwiegley@gmail.com>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] master 19e09cf: Ensure redisplay after evaluation
Date: Mon, 09 Nov 2015 21:17:11 +0200 [thread overview]
Message-ID: <83h9kvm18o.fsf@gnu.org> (raw)
In-Reply-To: <m2egfzhu0o.fsf@Vulcan.attlocal.net>
> From: John Wiegley <jwiegley@gmail.com>
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
> Date: Mon, 09 Nov 2015 11:06:47 -0800
>
> I am unaware of the historical context for this argument.
I can post the URL of the discussion. It was a very long discussion,
most of it dedicated to Stefan's review of the proposed patch. That
patch was eventually not admitted, because the author won't sign legal
papers as required by the FSF rules.
> Allowing dynamic behavior to trigger on modifying a variable could be very
> valuable during debugging. GDB allows this in the form of watchpoints.
>
> As long as we never allow the use of this facility to creep into Emacs itself,
> I can see value in giving users another way to debug and/or customize their
> environment, as long as they are fully informed of the potential costs.
I agree, but the problem is that now someone needs to re-implement
that changeset from scratch, without looking too much at the patch
posted back then. I cannot be that someone, unfortunately.
next prev parent reply other threads:[~2015-11-09 19:17 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83h9kvm18o.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jwiegley@gmail.com \
--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.