This is a symptom of the macOS App Translocation security feature - mentioned at http://moin.delph-in.net/LkbFos under ‘Problems’. I’m still thinking about how to fix this properly, but in the meantime just drag LKB.app out to another folder then back in. It should then work.
I’m running into this same problem now, except that moving LKB.app to a different folder and back (via drag & drop or mv in the terminal) just creates aliases and does not fix the problem. @johnca or @olzama — any other clever tricks I can try? Thanks!
Thanks, @johnca – that worked, but then the standard security override (ctrl-click to open) didn’t, so I tried this instead and LKB FOS is now running on my mac
I really miss the integration with emacs that I’m used to in linux, though. Is that a possibility in MacOS? (Sorry for all the naive questions!)
You can run emacs from the Terminal command line or from an XQuartz xterm, but the default version of emacs is 22.1.1 which is not recent enough to run SLIME, the lisp-emacs interface. Instead you could download emacs 27.1 from Emacs For Mac OS X and run that instead from Terminal, with
open /Applications/Emacs.app
But I think Aquamacs is a better alternative - as recommended in http://moin.delph-in.net/LkbFos. Follow the instructions in the section “Installation” and you’ll be able to run LKB-FOS inside emacs, just like in Linux.