all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: jwiegley@gmail.com, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] master 19e09cf: Ensure redisplay after evaluation
Date: Fri, 13 Nov 2015 10:06:52 +0200	[thread overview]
Message-ID: <83lha2gw6b.fsf@gnu.org> (raw)
In-Reply-To: <CAM-tV--c9tWomwLAv1e9dYSbFKWALpQk_Hr-QD0rvn0-q+iCUg@mail.gmail.com>

> Date: Thu, 12 Nov 2015 19:31:29 -0500
> From: Noam Postavsky <npostavs@users.sourceforge.net>
> Cc: John Wiegley <jwiegley@gmail.com>, Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
> 
> > 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.
> >
> 
> This functionality sounds very useful; I have definitely wanted
> something like this while debugging in the past.
> 
> Where should I look to get an idea of how to implement it?

In the discussion I pointed to.  You will have to make a conscious
effort to read just the discussion parts and skip the code attachments
parts.  That's not very easy, but doable: just don't open any
attachments, and whenever you see "diff --git" move one to the next
message in the thread.

Alternatively, Someone™ could re-read the discussion and post the
description of what the posted code did (without showing any actual
code), then you could write the code using only that description,
without looking at the actual code posted back then.  This is a better
method, I think.  Are there any volunteers for the first part, of
coming up with the description?  If no one steps forward, I could do
this myself, but I think this is a good opportunity for someone to
study a somewhat complicated issue related to how the Emacs Lisp
interpreter works.

TIA.




  reply	other threads:[~2015-11-13  8:06 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
2015-11-09 21:57           ` John Wiegley
2015-11-13  0:31           ` Noam Postavsky
2015-11-13  8:06             ` Eli Zaretskii [this message]
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=83lha2gw6b.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jwiegley@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=npostavs@users.sourceforge.net \
    /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.