You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The prof_post_chat_message_display hook is never invoked on the plugin side for chat history messages, only the prof_pre_chat_message_displayhook seems to be invoked.
$ profanity --version 2>&1 | sed -e 's/^/ /g'
Profanity, version 0.14.0
Copyright (C) 2012 - 2019 James Booth <[email protected]>.
Copyright (C) 2019 - 2023 Michael Vetter <[email protected]>.
License GPLv3+: GNU GPL version 3 or later <https://www.gnu.org/licenses/gpl.html>
This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Build information:
XMPP library: libstrophe
Desktop notification support: Enabled
OTR support: Enabled (libotr 4.1.1)
PGP support: Enabled (libgpgme 1.24.1)
OMEMO support: Enabled
C plugins: Enabled
Python plugins: Enabled (3.13.1)
GTK icons/clipboard: Disabled
GDK Pixbuf: Enabled
The text was updated successfully, but these errors were encountered:
What do you mean by chat history messages?
The limited history sent by the MUC? Or do you mean messages retrieved via MAM?
MAM support isn't finished yet. Is named experimental in the documentation. And is being worked on here #1862
Currently all messages are injected only with the
`pre_chat_message_display` hook which is not consistent how received and
sent chat messages receive the plugin.
We should discriminate between received and sent messages. Sent messages
should be injected with the `pre_chat_message_send` hook instead of the
`pre_chat_message_display` hook.
We should also call `post` hooks for both the received and the sent messages.
Fixes: profanity-im#2011
The
prof_post_chat_message_display
hook is never invoked on the plugin side for chat history messages, only theprof_pre_chat_message_display
hook seems to be invoked.debug
In the plugin hooks I just put this:
log
version
The text was updated successfully, but these errors were encountered: