@nick is there way to not have “autoname” show up in each extension name?
example snippet
// # popclip extension to search YouTube
// name: YouTube Search | ⌥ for YouTube Music
// icon: iconify:mdi:youtube
// requirements: ["!urls"]
// lang: js
const query = encodeURIComponent(popclip.input.text);
if (popclip.modifiers.option) {
popclip.openUrl("");
} else {
popclip.openUrl("");
}
No it’s fixed in the code. It’s not really intended as a “user facing” file name, more of an implementation detail. But I can see that there are ergonomic aspects to the naming. It the time I put that together I didn’t know if “snippets” (hadn’t named them that then … I called the feature “inception” in the code haha) would take off so it was all quite experimental. Of course once it’s done it sticks. It’s was mainly to have a prefix for the snippets (autoname as in “automatic file name”) and thus a unique name for every snippet that won’t clash with anything else … but still human readable for if you are digging around in there.
I have thought about changing it from “autoname” to “snippet” which might be less objectionable? 
nice!
It definitely isn’t objectionable 
. It can be easier to find/spot the snippet I’m finding if name starts with the snippet’s actual name. Some ideas I have is…putting them in a “snippets” directory and then they can have their own name…or, adding a suffix or autoname/snippet.