Hello,
Recently after switching branches in my SLIME Git repo I caught a message about slime/swank versions inconsistence. Presently SLIME urges to recompile slime.el if slime.elc is found and it older the slime.el, but it does not reloads slime.el automatically if it has been changed. The first solution which comes to the mind is the store md5 hashsum of the current slime.el and check it every time of SLIME loading. Thoughts?
On Sun, Dec 13, 2015 at 10:32 PM, Dmitry Igrishin dfigrish@gmail.com wrote:
Hello,
Recently after switching branches in my SLIME Git repo I caught a message about slime/swank versions inconsistence. Presently SLIME urges to recompile slime.el if slime.elc is found and it older the slime.el, but it does not reloads slime.el automatically if it has been changed. The first solution which comes to the mind is the store md5 hashsum of the current slime.el and check it every time of SLIME loading. Thoughts?
What does it provide that the modification date doesn't already do?
2015-12-14 11:31 GMT+03:00 Stas Boukarev stassats@gmail.com:
On Sun, Dec 13, 2015 at 10:32 PM, Dmitry Igrishin dfigrish@gmail.com wrote:
Hello,
Recently after switching branches in my SLIME Git repo I caught a message about slime/swank versions inconsistence. Presently SLIME urges to recompile slime.el if slime.elc is found and it older the slime.el, but it does not reloads slime.el automatically if it has been changed. The first solution which comes to the mind is the store md5 hashsum of the current slime.el and check it every time of SLIME loading. Thoughts?
What does it provide that the modification date doesn't already do?
It does provide automatic reloading slime.el which has not been compiled but has been changed.
-
Dmitry Igrishin -
Stas Boukarev