34 lines
1.1 KiB
Markdown
34 lines
1.1 KiB
Markdown
|
# Support
|
||
|
|
|
||
|
|
Prelude currently has several official & unofficial support channels.
|
||
|
|
|
||
|
|
For questions, suggestions and support refer to one of them. Please, don't
|
||
|
|
use the support channels to report issues, as this makes them harder to track.
|
||
|
|
|
||
|
|
## Gitter
|
||
|
|
|
||
|
|
Most internal discussions about the development of Prelude happen on its
|
||
|
|
[gitter channel](https://gitter.im/bbatsov/prelude). You can often find
|
||
|
|
Prelude's maintainers there and get some interesting news from the project's
|
||
|
|
kitchen.
|
||
|
|
|
||
|
|
## Mailing List
|
||
|
|
|
||
|
|
The [official mailing list](https://groups.google.com/forum/#!forum/emacs-prelude) is
|
||
|
|
hosted at Google Groups. It's a low-traffic list, so don't be too hesitant to subscribe.
|
||
|
|
|
||
|
|
## Freenode
|
||
|
|
|
||
|
|
If you're into IRC you can visit the `#prelude` channel on Freenode.
|
||
|
|
It's not actively
|
||
|
|
monitored by the Prelude maintainers themselves, but still you can get support
|
||
|
|
from other Prelude users there.
|
||
|
|
|
||
|
|
## Stackoverflow
|
||
|
|
|
||
|
|
We're also encouraging users to ask Prelude-related questions on StackOverflow.
|
||
|
|
|
||
|
|
When doing so you should use the
|
||
|
|
[Prelude](http://stackoverflow.com/questions/tagged/prelude) tag (ideally combined
|
||
|
|
with the tag `emacs`).
|