Yes, I used customize at first. When I write your suggestion above in my .emacs and open a .rkt file I get the error: File mode specification error: (void-variable racket-repl-buffer-name-unique) FWIW, I do have the function racket-repl-buffer-name-unique in racket-repl-buffer-name.el. Version is: GNU Emacs 27.1 (build 1, x86_64-w64-mingw32) of 2020–08–21.

In your Emacs init file, like .emacs, what if you do this

(require 'racket-mode) (setq racket-repl-buffer-name-function #'racket-repl-buffer-name-unique) That is similar to my personal config, except that I prefer the -project flavor as opposed to -unique.

That works. Thank you! I can also report that (setq racket-repl-buffer-name-function 'racket-repl-buffer-name-unique) works too.

Great!

I got in the habit of using #'x instead of 'x because it’s shorthand for (function x) — and when you byte compile, it raises an error if no such function exists. Which helps me avoid dumb mistakes like the one we’re talking about… except it doesn’t work in defcustom choice values.

Anyway it’s moot for your .emacs if you don’t byte-compile it. Which I don’t bother doing; Emacs starts fast enough. But I’m just in that habit of using #'. You don’t need to be, of course. :slightly_smiling_face:

Also I did push a commit last night to fix those customize default values. So someday if you update Racket Mode, you could just use customize again to change this. Sorry again for the problem.

Thank you for this customized assistance. Greatly appreciated. And thank you for racket-mode, which is really great. It “made Emacs great again” for me. :slightly_smiling_face: I upgraded to 27.1 only because of racket-mode.

@greg older versions of customize would double escape things… but never ones seem to be rolling that back to something more sensible…