Received: by 10.180.100.70 with SMTP id ew6mr207004wib.2.1353084086615; Fri, 16 Nov 2012 08:41:26 -0800 (PST) Path: q13ni319430wii.0!nntp.google.com!proxad.net!feeder1-2.proxad.net!78.46.93.83.MISMATCH!eu.feeder.erje.net!feeder.erje.net!us.feeder.erje.net!news.snarked.org!newsfeed.news.ucla.edu!usenet.stanford.edu!not-for-mail From: Tom Newsgroups: gnu.emacs.help Subject: Re: Diff could also show the changes within lines Date: Fri, 16 Nov 2012 16:40:56 +0000 (UTC) Lines: 22 Approved: help-gnu-em...@gnu.org Message-ID: References: <87txu9arc8.fsf@gmail.com> <80d2zlvnos.fsf@somewhere.org> <80vcd8l0h4.fsf@somewhere.org> <80zk2j3kkf.fsf@somewhere.org> <80obizp4fv.fsf@somewhere.org> <808va3p0ia.fsf@somewhere.org> <80d2zej3kd.fsf@somewhere.org> NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 X-Trace: usenet.stanford.edu 1353084086 30275 208.118.235.17 (16 Nov 2012 16:41:26 GMT) X-Complaints-To: action@cs.stanford.edu To: help-gnu-em...@gnu.org Envelope-to: help-gnu-em...@gnu.org X-Injected-Via-Gmane: http://gmane.org/ X-Gmane-NNTP-Posting-Host: sea.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 94.21.239.158 (Opera/9.80 (Windows NT 6.1) Presto/2.12.388 Version/12.10) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: help-gnu-em...@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Stefan Monnier iro.umontreal.ca> writes: > > If you let-bind diff-auto-refine-mode to nil in the above code, not only > you'll be able to test it on Emacs-24.1 (and earlier), but you'll avoid > refining the hunks redundantly when diff-hunk-next does it. Good suggestion. Thank you. What I did not get in the new diff-mode implementation is why it uses run-at-time instead of run-with-idle-timer? run-at-time is for specifying a timer which runs at a specific time while run-with-idle-timer runs it when emacs becomes idle. Isn't using run-with-idle-timer is more appropriate (makes the code clearer) in this case? And why the code uses 0.0 instead of just 0? Is there a difference?