Proposal: Add package to Nongnu Elpa (or Melpa)?

[mmarshall540]

I'm not sure what's involved with adding a package to Nongnu Elpa. But adding it either there or to Melpa would make set-up easier and improve discoverability for Kmonad, since that would cause it to be listed with the other packages available from list-packages.

Nongnu Elpa is included in the default set-up for Emacs 28. So adding it there would be preferable since users wouldn't even have to add Melpa to package-archives. If the package were available on NonGnu Elpa, a user could add it to a fresh Emacs install simply by doing "M-x package-install RET kbd-mode RET", or by searching and clicking the install button after doing M-x list-packages RET.

But inclusion in Nongnu Elpa seems to be at the discretion of the Emacs maintainers. If for some reason that were a hindrance, adding the package to the Melpa repository would provide nearly the same benefit. The only difference being that Melpa has to be manually added to package-archives (but of course, that's something most Emacs users do already).

[slotThe]

I think adding it to NonGNU ELPA (or MELPA, I have really no preference here). However, I want to get this hack out of the code first (I'm neither happy with this, nor do I expect it to pass code review on either of the two package archives).

I've had "change KMonad's parser to disallow literal "s (i.e., close this issue)" on my TODO list for quite a while, but I haven't found the time for it so far. Contributions welcome!

[mmarshall540]

Wish I could help with the Kmonad part of this, but I have no knowledge of Haskell. I might look deeper into the elisp hack to see if there's a way to handle it using the syntax table or some other method. It's a learning experience for me more than anything.