ison writes: > My understanding of the global definitions they're talking about is that > they would just be meta objects, not global preferences. > For example (maybe it won't look like this, but just a guess): > Instead of passing the arguments "mpv" and "3.7" into your function you'd > give the parameters: > '((video-player . "mpv") > (python-version . "3.7")) > to the package. > video-player and python-version would be globally defined meta objects > that just give descriptions about what these parameters should be used for > and such (so users can read more information about package parameters when > looking up packages). But the actual values that get used by the package > are not global, they're passed into the package just like your function > example. > > I hope I'm not missing something here, but this is how I was reading the > conversation. You are correct, this is precisely what I meant. Does that make more sense, Simon? -- Pierre Neidhardt https://ambrevar.xyz/