Offer to help with bytecode mismatches?

[greghendershott]

When working on a project that's been compiled -- that has compiled subdir(s) created by raco make or raco setup -- eventually you can get this error:

link: module mismatch; possibly, bytecode file needs re-compile because dependencies changed

The solution is to rm -rf compiled/ or re-run raco make or raco setup. Which isn't difficult to do. But it's kind of a buzz-kill flow-breaker to need to M-x shell, cd to the right directory, issue the rm or raco command... then remember what you were focused on before this annoying distraction.

Could racket-mode notice this sort of error, and do something automatically? Maybe after a y/n prompt?

[greghendershott]

See https://github.com/rmculpepper/custom-load

[cpitclaudel]

Instead of going to a separate shell, I would expect users to use M-x compile and put raco make in there. We could help by setting compile-command to raco make by default:

compile-command is a variable defined in ‘compile.el’.
Its value is "make -k "

  This variable may be risky if used as a file-local variable.
  This variable is safe as a file local variable if its value
  satisfies the predicate ‘(lambda (a) (and (stringp a) (or (not (boundp (quote compilation-read-command))) compilation-read-command)))’.

Documentation:
Last shell command used to do a compilation; default for next compilation.

Sometimes it is useful for files to supply local values for this variable.
You might also use mode hooks to specify it in certain modes, like this:

    (add-hook 'c-mode-hook
       (lambda ()
     (unless (or (file-exists-p "makefile")
             (file-exists-p "Makefile"))
       (set (make-local-variable 'compile-command)
        (concat "make -k "
            (if buffer-file-name
              (shell-quote-argument
                (file-name-sans-extension buffer-file-name))))))))

You can customize this variable.