Hi! I'm one of the maintainers of copilot.el. We recently added built-in chat support under the copilot-chat feature name, which is part of our copilot- namespace.
Unfortunately this creates a hard conflict with your package — both projects define a copilot-chat feature and overlapping symbols, making them impossible to use side by side. We've been getting bug reports from confused users:
Since copilot.el has used the copilot- prefix since 2022 and is distributed on MELPA under that name, the prefix is effectively claimed per standard Elisp namespace conventions. We'd rather not rename our own feature to work around the collision.
Would you consider renaming this package to use a different prefix? Some ideas:
wingman-chat — distinctive and memorablechep-copilot-chat — uses your own namespace as a prefix
I realize renaming is disruptive and I appreciate the work you've put into this project. Happy to discuss alternatives if none of these work for you.
Hi! I'm one of the maintainers of copilot.el. We recently added built-in chat support under the
copilot-chatfeature name, which is part of ourcopilot-namespace.Unfortunately this creates a hard conflict with your package — both projects define a
copilot-chatfeature and overlapping symbols, making them impossible to use side by side. We've been getting bug reports from confused users:Since
copilot.elhas used thecopilot-prefix since 2022 and is distributed on MELPA under that name, the prefix is effectively claimed per standard Elisp namespace conventions. We'd rather not rename our own feature to work around the collision.Would you consider renaming this package to use a different prefix? Some ideas:
wingman-chat— distinctive and memorablechep-copilot-chat— uses your own namespace as a prefixI realize renaming is disruptive and I appreciate the work you've put into this project. Happy to discuss alternatives if none of these work for you.