-
-
Notifications
You must be signed in to change notification settings - Fork 403
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
help: using a pastebin should be optional #1212
Comments
Also additional options, like outputting to a text or HTML file on the local filesystem instead, would be useful. Maybe I should just bite the bullet and implement all that. |
As an aside, this issue might be obsolete. See #1254. |
Switched to a different pastebin provider for the time being. This will stick around as a feature request. |
I feel like this has been fixed by #1451 |
Punting this. The implementation should add an option without changing the existing behavior if not configured, so no rush to get this into the next major version. |
The more I think about that one, the more I'd like to create a separated package for the help plugin, and to have a dedicated For instance, I'd love to allow third-party devs to implement their own help publishing backend, so whenever someone have a new use-case that is solely for them and their group, they could do it more easily. Also, I'd use it as an excuse to push Sopel's internals to always be better - as one may say "eat your own food". |
Aren't we already pulling a bunch more stuff out of core for 8.0? |
Yes, but I'd love to start with Also, "help" is another name for "documentation". 😛 |
Feel free to play around in the new |
We'll consider this fixed by sopel-irc/sopel-help, which includes several pastebins, adds local HTML output (to be served by the user's chosen external HTTPd), and resurrected direct-to-IRC output as well. Since the new plugin only supports Python 3.5+, I'll mark this for Sopel 8.0 (which will drop support for older Python versions) and note it prominently in the release notes for that version, then close the issue. |
Not all environments are public environments where it is appropriate to post commands publicly. It would be extremely helpful if this behavior (print to channel or gist) was configurable.
The text was updated successfully, but these errors were encountered: