Open jscheid opened 1 year ago
Would you like to take ownership of this project, Julian? I'm mostly retired from Emacs, and I certainly wouldn't be a "reasonably active maintainer." I invited you as a collaborator and began a transfer. Feel free to move the project under your username or whatever is convenient. I don't expect to touch this project again myself. Let me know if there's anything else I can do to help hand this off!
Sure, why not. Thanks, I've accepted the invitation and I'll start getting things into shape for MELPA release. I think I'm all set for now, I'll let you know if I need anything. Thanks again. Out of curiosity, may I ask where you defected to? Visual Studio Code? Hammock?
I picked up modal editing five years ago — a great move, and something I should have done much sooner — and Vim has been my primary editor ever since:
https://nullprogram.com/blog/2017/04/01/
I've gone completely opposite and hardly customize it. No plugins, merely a .vimrc that addresses some of Vim's poor defaults. I had tried Evil for awhile, which I used to write this project (only 4 years old). It's still the best Vim emulation I've yet come across, but at least when I tried it, too often I needed to fall back to Emacs keybindings.
I also distribute my own Vim build as part of a C and C++ development kit:
https://github.com/skeeto/w64devkit
Due to its limited cross-compilation support, this would not have been possible with Emacs. (Even if it were, it would more than double the site of my whole kit.) Such flexibility even further cemented Vim for me. My kit's out-of-the-box experience, including ctags, is representative of how I work these days.
Wait a second, you're the Chris Wellons! I've read so much of your stuff, you're probably the best resource of low-level Elisp on the planet. I can't believe you're off... it'll take me a while to wrap my head around this.
Thanks for the pointers -- I'll dig into it on a less busy day.
Hi, thanks for this package.
Would you help me get it onto MELPA so that I can use it as a dependency?
We'd need to address these issues raised by
package-lint
and have a "reasonably active maintainer", does that sound like you?I'm happy to pitch in as much as I can, with PRs and handling comms with the MELPA guys.