diff options
| author | Richard van der Hoff <richard@matrix.org> | 2018-05-23 13:58:28 +0100 |
|---|---|---|
| committer | Richard van der Hoff <richard@matrix.org> | 2018-05-23 13:58:28 +0100 |
| commit | 1cbb8e5a33326441ec311ce212bb62fcd6704669 (patch) | |
| tree | f68d28197456e980ffab81e14e8a04e0c2c96bbe | |
| parent | Using the manhole to send server notices (diff) | |
| download | synapse-1cbb8e5a33326441ec311ce212bb62fcd6704669.tar.xz | |
fix wrapping
| -rw-r--r-- | docs/server_notices.md | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/docs/server_notices.md b/docs/server_notices.md index a96a5b88a3..9896881389 100644 --- a/docs/server_notices.md +++ b/docs/server_notices.md @@ -59,7 +59,9 @@ As of the current version of synapse, there is no convenient interface for sending notices (other than the automated ones sent as part of consent tracking). -In the meantime, it is possible to test this feature using the manhole. Having gone into the manhole as described in [manhole.md](manhole.md), a notice can be sent with something like: +In the meantime, it is possible to test this feature using the manhole. Having +gone into the manhole as described in [manhole.md](manhole.md), a notice can be +sent with something like: ``` >>> hs.get_server_notices_manager().send_notice('@user:server.com', {'msgtype':'m.text', 'body':'foo'}) |