Getting macros for Emacs right is an abysmal pita, as the output of the macro must be valid Elisp code. This usually requires a wild mix of expansion/evaluation or not of the macro parameters in the right places. If you have not done this for the last umpteen years, you will (no subjunctive, you WILL) screw up first.
To make the task a easier I tried a macro to (a) dump the macro expansion of your macro and (b) let it go wild.
https://codeberg.org/harald/Codeschnipselnotizen/src/branch/main/elisp/tracemacro.el
I get the feeling that a lot of folks think they can ride out climate change, that their affluence will keep them relatively safe, that it’s a distant concern that will come for Those Other People first.
To that I say: You really think you’re more protected than Billy Crystal? Carry Elwes? Eugene Levy? Paris Hilton? John Goodman? They all just lost their homes, despite all the fame and fortune a person could wish for. What's keeping •you• safe? The answer, I’m afraid, is “nothing but luck.”
In shock news, LinkedIn uses your data to train Microsoft (who own it, remember) and its own AI models. And of course that's turned on by default without asking your permission first.
To refuse permission on the LinkedIn website:
Me > Settings & Privacy > Data Privacy > Data for Generative AI Improvement
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.