about summary refs log tree commit diff stats
path: root/src/event
Commit message (Collapse)AuthorAgeFilesLines
* Pass window to functions so we dont have to call twiceMichael Vetter2020-07-091-1/+1
|
* Apply coding styleMichael Vetter2020-07-074-258/+255
|
* Revert "Apply coding style"Michael Vetter2020-07-075-273/+276
| | | | | | This reverts commit 9b55f2dec0ea27a9ce4856e303425e12f866cea2. Sorting the includes creates some problems.
* Apply coding styleMichael Vetter2020-07-075-276/+273
| | | | Regards https://github.com/profanity-im/profanity/issues/1396
* Plain chat messages not workingDebXWoody2020-07-061-4/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Plain chat messages not working for non-carbon + no OTR support. On master we did some clean-up. The problem is at https://github.com/profanity-im/profanity/blob/0.9.patch/src/event/server_events.c#L625 (0.9.0). The implementation looks like: - HAVE_LIBOTR is set - _sv_ev_incoming_otr - HAVE_LIBOTR is not set - _sv_ev_incoming_plain I think the `_sv_ev_incoming_otr` can handle otr and plain, because I didn't find a `_sv_ev_incoming_plain` if `HAVE_LIBOTR` is set. On master for 0.10.0 the implementation is much better: https://github.com/profanity-im/profanity/blob/master/src/event/server_events.c#L623 But, we just call `_sv_ev_incoming_otr` independent of `HAVE_LIBOTR`. Unfortunately, `_sv_ev_incoming_otr` is doing nothing if `HAVE_LIBOTR` is not set: https://github.com/profanity-im/profanity/blob/master/src/event/server_events.c#L538 I did some more clean-up at sv_ev_incoming_message and changed the implementation of `_sv_ev_incoming_otr`. ``` static void _sv_ev_incoming_otr(ProfChatWin *chatwin, gboolean new_win, ProfMessage *message) { // OTR or plain plain } ``` The caller do not take care of `HAVE_LIBOTR`, call `_sv_ev_incoming_plain` if you are sure it's a plain message or call `_sv_ev_incoming_otr`. `_sv_ev_incoming_otr` can be used for otr / plain or for plain only.
* Remove prefs_free_string()Michael Vetter2020-07-021-5/+5
| | | | | It just does a free. Related to b580b9ef119045f142fa4baa9689a1c5ce8864ef
* And ifdefs around new OX functionsMichael Vetter2020-06-301-1/+1
| | | | | Fix for some build cases introduced in 2c94ee5a88f64332a3f41f41a4d314fc52200e31 Fix https://github.com/profanity-im/profanity/issues/1376
* Feature request - XEP-0373: OpenPGP for XMPP (OX)DebXWoody2020-06-292-2/+31
| | | | | | | | | Basic implementation of XEP-0373: OpenPGP for XMPP. https://xmpp.org/extensions/xep-0373.html Command /ox Issue: #1331
* Cleanup defines - client_events.cDebXWoody2020-06-191-179/+5
|
* Clean-up task: clean up feature definesDebXWoody2020-06-141-201/+8
|
* Add option for legacy authenticationDmitry Podgorny2020-06-052-3/+3
| | | | | | | | New options: /connect <account> [auth default|legacy] /account <account> set auth default|legacy Fixes #1236.
* Fix offline roster contactsMichael Vetter2020-06-021-1/+2
| | | | | | | | | | | | | | | | | Fix https://github.com/profanity-im/profanity/issues/1280 p_contact_set_presence() is triggered in (roster_process_pending_presence) to set the presence to online after the roster is displayed. This happened to me _every time_ with one certain account on my server. But not even once with other accounts on my server. I don't understand why that is the case, but AFAIK the code should be like it is in this PR anyways. roster_process_pending_presence() was added there in 973a05d15a9843f2e8f6dff598f2161367885994 to fix https://github.com/profanity-im/profanity/issues/1050
* Merge pull request #1344 from DebXWoody/bugfix/1327Michael Vetter2020-05-281-2/+1
|\ | | | | Bugfix: Status with PGP shows offline in titlebar
| * Bugfix: Status with PGP shows offline in titlebarDebXWoody2020-05-231-2/+1
| | | | | | | | | | | | | | | | There is code to redraw the ui, because the user may enter a passphase for the private key. There was also a ui_init, which shouldn't be called, because it will set the status to the initial state, which is 'offline' and 'no tls'. Issue: #1327
* | Fix carbon loggingMichael Vetter2020-05-271-6/+4
| | | | | | | | Regards https://github.com/profanity-im/profanity/issues/1342
* | Add and use connection_get_barejid()Michael Vetter2020-05-252-7/+6
| | | | | | | | Instead of connection_get_fulljid() and then creating a Jid from it.
* | Add bookmark ignore functionality for multiple accountsMichael Vetter2020-05-242-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | ``` cat ~/.local/share/profanity/bookmark_ignore [jubalh@iodoru.org] profanity@rooms.dismail.de=true [testuser@domain.org] testr@rooms.domain.org=true ``` Regards https://github.com/profanity-im/profanity/issues/1115
* | PoC for bookmark ignoreMichael Vetter2020-05-241-0/+6
|/ | | | | | | | | | ``` ~/.local/share/profanity % cat bookmark_ignore [ignore] profanity@rooms.dismail.de= ``` Regards https://github.com/profanity-im/profanity/issues/1115
* Log all carbon copied messagesMichael Vetter2020-05-221-0/+1
| | | | | | | So far we only had the logging in sv_ev_incoming_carbon() not sv_ev_outgoing_carbon(). Regards https://github.com/profanity-im/profanity/issues/1342
* Add option to add bookmark nameMichael Vetter2020-05-221-1/+1
| | | | | | | | `/bookmark add|update` got `name` field. By default localpart of JID is used (like before) but now we can set the name ourselves. Regards https://github.com/profanity-im/profanity/issues/697
* MAM: Correctly display incoming MAM chat messageMichael Vetter2020-04-111-5/+19
|
* Add to_jid field to ProfMessage structMichael Vetter2020-04-111-33/+35
| | | | | Is usefult in many cases if we want cleaner code. Hope this edit didn't break anything though ;-)
* Log after displaying the messageMichael Vetter2020-04-081-6/+6
| | | | | | | | Otherwise we print the freshly received message to the window twice. Once when receiving (and immediately printing), then logging it, and then again when we print the last 10 log entries. Fix https://github.com/profanity-im/profanity/issues/1305
* db: Use type from message struct instead of having individual functionsMichael Vetter2020-04-061-7/+7
|
* Add type field to ProfMessageMichael Vetter2020-04-061-1/+1
| | | | The mucuser boolean is not now needed anymore.
* Fix copy paste errorMichael Vetter2020-04-061-1/+1
|
* db: dont log reflected MUC messagesMichael Vetter2020-04-061-1/+1
|
* db: log all incoming and outgoing messagesMichael Vetter2020-04-061-2/+22
|
* db: log outgoing message in one caseMichael Vetter2020-04-061-0/+2
| | | | Not all cases covered yet.
* db: add dedicated chat, muc, muc pm logging functionsMichael Vetter2020-04-061-7/+7
|
* Rename PROF_MSG_ENC_PLAIN to PROF_MSG_ENC_NONEMichael Vetter2020-04-062-19/+19
|
* db: insert message typeMichael Vetter2020-04-061-6/+7
|
* db: move includesMichael Vetter2020-04-061-1/+1
|
* db: Have one database per accountMichael Vetter2020-04-062-0/+4
|
* database: dont log muc pmsMichael Vetter2020-04-061-2/+0
|
* database: log stanza_id and whether it is a muc messageMichael Vetter2020-04-061-8/+8
|
* database: log incoming messagesMichael Vetter2020-04-061-0/+9
| | | | First trial. Not covering all cases yet.
* Dont filter out own MUC messages if muc history is set to 'regular'Michael Vetter2020-02-211-1/+1
| | | | | | | | 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
* Fix missing change from last commitMichael Vetter2020-02-201-1/+1
|
* Allow utf8 symbols as omemo/pgp/otr indicator charMichael Vetter2020-02-201-1/+1
| | | | Fix https://github.com/profanity-im/profanity/issues/1264
* Put getting mentions in own functionMichael Vetter2020-02-201-10/+1
| | | | | | So we can use it somewhere else too. Regards https://github.com/profanity-im/profanity/issues/1261
* Refactor mucwin_history()Michael Vetter2020-02-191-1/+1
| | | | Just pass ProfMessage.
* Always send delivery receipts if enabledMichael Vetter2020-02-141-14/+1
| | | | | | | | | | | | | So far receipts are only send if we have enabled it and the other client supports it. But it could be that the other person is connected with several clients. One supporting it and the other which doesn't. If the not supporting one is active and we send to a fulljid, then we won't get receipts. Probably it's best to just always send them if they are enabled in Profanity. And not try to find out the capabilities of the other client. Fix https://github.com/profanity-im/profanity/issues/1268
* Fix testsMichael Vetter2020-02-141-7/+7
|
* xep-0308: remove replace_id from privwin signatureMichael Vetter2020-02-141-1/+1
| | | | No `/correct` allowed in privwins
* xep-0308: Implement LMC for outgoing MUC messagesMichael Vetter2020-02-142-8/+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: Dont allow to correct MUC PMsMichael Vetter2020-02-141-1/+0
| | | | | People could change messages of other people if the nick isn't registered.
* xep-0308: enable corrections for outgoing encrypted messagesMichael Vetter2020-02-121-21/+21
|
* xep-0308: update the UI upon sending a corrected messageMichael Vetter2020-02-111-5/+6
| | | | | So far we don't do this for encrypted messages. Still needs to be done. And MUC also needs to be done.
* xep-0308: Implement `/correct` to correct the last send messageMichael Vetter2020-02-102-7/+20
| | | | | | | | So far the correction is sent. But the UI in Profanity itself is not updated. Also autocompletion for `/correct` with the last sent message is missing.
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-01 11:26:25 +0000