Trust the default perspective scratch buffer contents

[elken]

Without this, by default trying to interact with a new perspective
puts the "Disabline elisp-flymake-byte-compile due to untrusted
content" message to popup in the minibuffer creating an annoying UX.

Regular scratch should trusted in Emacs[1][2] but that doesn't propogate
here

[1] https://lists.gnu.org/archive/html/emacs-devel/2025-02/msg01023.html
[2] emacs-mirror/emacs@8b6c6cffd1f7

[gcv]

I just read the mailing list thread, and have more questions than answers from it. Is there maybe an official function that we can call that makes a new scratch buffer we can call that does the official right thing? I don't feel comfortable setting such a sensitive setting on the user's behalf.

[elken]

Doesn't look like it no, lisp-interaction-mode should be setting it as well but it doesn't seem to be.

Maybe a less-destructive solution here is putting it behind a defcustom that's nil by default? persp-trust-scratch-buffers or something

[gcv]

Since flymake seems to be the only reason this warning shows up, how about we just disable it for perspective scratch buffers? It should be a very uninvasive change.

[elken]

Sensible change if that fixes it, I'll test it today 👍

[elken]

Thanks for the suggestion @gcv, this seems to also fix it!

Please do test yourself to verify but I'm happy this also works 😄

[gcv]

I’m not sure when flymake-mode was added to Emacs, but just in case, can we only run that deactivation when the flymake-mode function is definitely available?

[elken]

First added in Emacs 23, but yes it's a trivial addition 😄

[gcv]

Looks good, thanks!