On Sun, Jan 12 2014, João Távora wrote:
The testing code is probably the easiest to move.
OK, nice. What's second-easiest? :-)
Then create your "backend" directory. If that finally stops this game.
Actually, it might be good to move everything related to contribs to a contrib. So that SLIME, including slime-autoloads, doesn't need to know that contribs exist.
But at least the variable "slime-contribs" and "slime-setup" must be there, I think. Well as long we don't break any existing recipes.
slime-contribs is new; it wasn't there before.
"urge-recompile" doesn't sound obsolete as long as Emacs loads .elc files that are older than the corresponding .el file.
"make compile" checks mtimes. Would you be willing to use something like this in your ~/.emacs instead?
(defadvice slime (before slime-urge-bytecode-recompile activate) (let ((default-directory slime-path)) (unless (zerop (shell-command "make compile 2>&1 | tail -1 | grep '0 files compiled'")) (when (and (file-readable-p "slime.elc") (y-or-n-p "Reload slime.elc?")) (load "slime.elc")))))
Or moving that code to that slime-debugging contrib?
It's not about me. It's about people who do "git pull" then forget "make compile".
Helmut