[O] Bug: Lexical scoping in org-clock.el seems to break `org-clock-load' [9.0 (9.0-elpaplus @ /home/exot/.emacs.d/elpa/org-plus-contrib-20161102/)]

[Daniel Borchmann]

Remember to cover the basics, that is, what you expected to happen and
what in fact did happen.  You don't know how to make a good report?  See

     http://orgmode.org/manual/Feedback.html#Feedback

Your bug report will be posted to the Org mailing list.
------------------------------------------------------------------------

Loading a persistent clock does not work anymore: the hooks installed by
‘org-clock-persistence-insinuate’ call ‘org-clock-load’ as usual, but
the latter does not resume the clock: it prints "Restoring clock data",
but nothing else happens.

A closer look into ‘org-clock-load’ reveals that it introduces a local
variable ‘resume-clock’.  This variable is supposedly set by the line
‘(load-file filename)’ (line 2977 of org-clock.el), where ‘filename’ is
bound to ‘org-clock-persist-file’.  However, this call does not change
the local value of ‘resume-clock’ (it stays nil), but instead introduces
the variable ‘resume-clock’ with the corresponding value to the global
namespace.  Consequently, the clock is not resumed.


Emacs  : GNU Emacs 25.1.1 (x86_64-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
 of 2016-10-24, modified by Debian
Package: Org mode version 9.0 (9.0-elpaplus @ 
/home/exot/.emacs.d/elpa/org-plus-contrib-20161102/)
-- 
Daniel Borchmann
GPG (Mail)            0849 473E 6BF0 B504 DF0B  D640 455E 3610 01FF 778F
.
Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html