▲ | zitterbewegung 7 months ago | ||||||||||||||||||||||
Largely this problem which is core to Emacs in the sense it literally is "An Elegant Weapon For A More Civilized Time" due to its age. There is no concept of sandboxing anything in Emacs. You do get an alert sometimes when you change Theme's since they have a notion of totally executable code. Maybe a better solution would be to make a subset of elisp that artifacts be coded in which are sandboxed. | |||||||||||||||||||||||
▲ | d0mine 7 months ago | parent | next [-] | ||||||||||||||||||||||
No sandboxing is not a bug, it is the feature that makes emacs into elisp platform, and not just another editor that has defined API for extensions. | |||||||||||||||||||||||
▲ | taeric 7 months ago | parent | prev [-] | ||||||||||||||||||||||
This problem is specific to elisp evaluation. It is rare that you would want to work in elisp code and not be modifying your currently running emacs. If you are working on code for any other language, it is probably using an LSP or other form of child processes, right? | |||||||||||||||||||||||
|