about summary refs log tree commit diff stats
path: root/src/ui/mucwin.c
Commit message (Collapse)AuthorAgeFilesLines
* Dont filter out own MUC messages if muc history is set to 'regular'Michael Vetter2020-02-211-3/+3
| | | | | | | | We use the same incoming function as for regular incoming text here. But don't want to filter out our own messages since we didn't print them during sending. Follow up to 8ee2cdadc88978ea26e6b6eb56f2aaa1fd5a81df
* Allow utf8 symbols as omemo/pgp/otr indicator charMichael Vetter2020-02-201-84/+91
| | | | Fix https://github.com/profanity-im/profanity/issues/1264
* Parse mentions and triggers in muc history if display is 'regular'Michael Vetter2020-02-201-19/+26
| | | | Fix https://github.com/profanity-im/profanity/issues/1261
* Add option to color MUC history like regular messagesMichael Vetter2020-02-201-1/+12
| | | | | | | | | `/logging group color` has: * `unanimous` which will color it with one unanimous color. Like it was done always. * `regular` which colors it like regular incoming messages. Regards https://github.com/profanity-im/profanity/issues/1261
* Refactor mucwin_history()Michael Vetter2020-02-191-6/+7
| | | | Just pass ProfMessage.
* Refactor win_print_history()Michael Vetter2020-02-171-1/+1
| | | | We never use the printf like behaviour anyways.
* Refactor win_print_outgoing_muc_msg()Michael Vetter2020-02-171-1/+1
| | | | We never use the printf like behaviour anyways.
* Refactor win_println_incoming_muc_msg()Michael Vetter2020-02-171-1/+1
| | | | We never use the printf like behaviour anyways.
* Rename `win_println_them_message()` -> `win_println_incoming_muc_msg()`Michael Vetter2020-02-141-1/+1
| | | | | | | | In aa3693daa211b36c78d136d5a1ee9f3258e21352 I renamed `win_println_me_message()` -> `win_print_outgoing_muc_msg()`. Now: `win_println_them_message()` -> `win_println_incoming_muc_msg()` to be more consistent and descriptive.
* xep-0308: Implement LMC for outgoing MUC messagesMichael Vetter2020-02-141-2/+19
| | | | | | Including OMEMO encrypted ones. Also rename `win_println_me_message()` to `win_print_outgoing_muc_msg() as I think it's a more descriptive name.
* xep-0308: Display corrected incoming MUC messages correctlyMichael Vetter2020-02-121-1/+1
|
* Update my Copyright to 2020Michael Vetter2020-01-031-1/+1
|
* separator: Enable for MUC and PRIVWIN tooMichael Vetter2019-12-131-0/+2
| | | | Fix https://github.com/profanity-im/profanity/issues/1238
* Add vim modelineMichael Vetter2019-11-131-0/+1
|
* Don't override ProfMessage Id with origin-idMichael Vetter2019-10-311-1/+1
| | | | | | | | | | Profanity sends the same value for both. Other clients might not. Safe both since we could need them later. Once we implement Last Message Correction we will need the regular id. If we override it with origin-id and another client chooses to not use the same value for id and origin-id then we can't interpret the id sent with the LMC request correctly.
* Replace sent_messages list with algoMichael Vetter2019-10-311-3/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | For OMEMO we had a list with our sent messages. It was used so that we don't decrypt our own messages in MUCs that come in via reflection. Recently for https://github.com/profanity-im/profanity/pull/1209 we started to use origin-id and use an algorithm so we can detect our own sent messages via checking origin-id. Profanity uses the same id for the message ID and origin-id. With 06f300a42c4c627b6f1817bd48d92f083ffd9883 we added the message_is_sent_by_us() function. We implemented XEP-0359 this way to fix https://github.com/profanity-im/profanity/issues/1201 so that we don't log our own messages in MUCs twice. We can now check whether the message was sent by us using this function and can get rid of the list. Probably we could also put many parts of the sv_ev_room_message() function inside (else) part of `if (!(g_strcmp0(mynick, message->jid->resourcepart) == 0 && message_is_sent_by_us(message))) {`. Have to look more closely whether any of this needs to be run in case the message actually comes from us.
* Remove not needed codeMichael Vetter2019-09-291-4/+0
| | | | Was left over from refactoring a long time ago.
* Rename prof_message_t into ProfMessagePaul Fariello2019-06-201-1/+1
|
* Set foreground color for untrusted messagesPaul Fariello2019-06-201-1/+1
|
* Add prof_message_t to wrap all message attributesPaul Fariello2019-06-201-15/+20
| | | | | | | Probably missing copy of body to plain in carbon and privmessage. Only covers the incoming message path because goal is OMEMO decryption of untrusted message. Cover some of the log functions but not all.
* Add myself to copyrightMichael Vetter2019-06-171-0/+1
| | | | Like discussed with James.
* Safe last MUC message timestamp per MUCMichael Vetter2019-06-111-0/+2
| | | | | | After pasis review of my code he thinks it's better to safe the timestamp per MUC so we can account for some problems that could occur with timing.
* Handle MUC anonymous state when auto starting OMEMOPaul Fariello2019-04-171-1/+1
| | | | | | | When auto joining a MUC we don't have access to required information so we just don't start OMEMO at this time. Once we receive disco info we then try to start OMEMO.
* Add OMEMO policyPaul Fariello2019-04-171-0/+19
| | | | | | | | | | | | There is 3 policy: - manual: OMEMO session are only started manually - automatic: OMEMO session are only started if they have been started manually before - always: OMEMO session are always started unless they have been ended manually before Closes #1040 and fixes #1052
* Handle message without id in MUCPaul Fariello2019-04-141-1/+1
| | | | Some clients seems to send message without id.
* Rework MUC reflected message filteringPaul Fariello2019-04-101-2/+9
| | | | | | | | | Reflected messages can't be filtered by nick only otherwise you might ignore messages comming from you on another devices. Consequently we maintain a list of sent messages id in mucwin. To be sure the id will be correctly reflected we use the origin-id stanza.
* Log and print outgoing encrypted messagePaul Fariello2019-04-101-11/+35
|
* Fix /me display when highlighting user in MUCsMichael Vetter2019-02-261-8/+14
| | | | | Fixes https://github.com/boothj5/profanity/issues/950 Closes https://github.com/boothj5/profanity/pull/992
* Update copyright to include 2019Michael Vetter2019-01-221-1/+1
|
* Do not highlight room tab on subject changeJames Booth2018-03-101-11/+0
|
* Add preferences for tab displayJames Booth2018-03-091-6/+6
|
* Show name in statusbar tabs WIPJames Booth2018-03-081-6/+6
|
* Update copyrightJames Booth2018-01-211-1/+1
|
* Update CopyrightJames Booth2017-01-281-1/+1
|
* Allow room display properies to be set by pluginsJames Booth2017-01-201-4/+45
|
* Add win highlight fuctionsJames Booth2016-10-151-12/+12
|
* Add win_print_historyJames Booth2016-10-151-1/+1
|
* Add win_appendJames Booth2016-10-151-16/+16
|
* Add win_appendlnJames Booth2016-10-151-12/+11
|
* Add win_printJames Booth2016-10-151-77/+77
|
* Use win_printf_line where appropriateJames Booth2016-10-151-56/+56
|
* Add ch arg to win_printf_lineJames Booth2016-10-151-9/+9
|
* Use THEME_DEFAULTJames Booth2016-10-141-42/+42
|
* Add win_printf_lineJames Booth2016-10-141-9/+9
|
* Always use string format in win_printfJames Booth2016-10-121-11/+11
|
* Remove win_print, use win_printf insteadJames Booth2016-10-111-53/+53
|
* Rename win_vprint -> win_printfJames Booth2016-10-111-64/+64
|
* Tidy headersJames Booth2016-07-241-3/+3
|
* Update GPL link in headersJames Booth2016-07-241-1/+1
|
* Define stanza's attributes as const char*Dmitry Podgorny2016-04-271-2/+2
| | | | | | | | | | | | In most get-like funcitons libstrophe returns pointer to a string that resides in an internal structure (e.g. xmpp_stanza_t). Hence, Profanity must not change such strings. Define respective variables as 'const char*' to reduce a chance of error and conform future libstrophe's interface. This patch mostly replaces 'char *' with 'const char*', but also fixes two memory leaks after stanza_get_reason(). Add comment within stanza_get_reason() to fix conflict with different allocator types.
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-01 10:32:18 +0000