about summary refs log tree commit diff stats
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
...
* Remove autocompletion for unanimous/regular colorMichael Vetter2020-05-161-12/+0
| | | | See 85520ecdc5d2e6ac6654817572b8fd99e43e25d9
* xep-0092: make it possible to ask servers or components for softwareMichael Vetter2020-05-144-17/+65
| | | | | | | | | | | This adds the new `/serversoftware` command. ``` /software user@domain.org/resource /serversoftware domain.org ``` Fix https://github.com/profanity-im/profanity/issues/1338
* Have proper autocompletion for /software in chat windowMichael Vetter2020-05-142-17/+60
| | | | | | | | | | | In console autocomplete from roster. In muc autocomplete from occupants lits. In 1:1 regular chat autocomplete from active resources of currently selected user (new). Also give a hint (/help resource) how to set the resource should a user choose that way. Fix https://github.com/profanity-im/profanity/issues/1337
* Fix `/correction` char displayMichael Vetter2020-05-061-1/+1
| | | | | https://github.com/profanity-im/profanity/commit/1f8b1eb740391941e79e1004ad041f8178a2b674 made it possible to have utf8 chars as correction chars. So since then prefs_get_correction_char() doesn't return a regular char but a char*. Seems like there was an oversight that we need to use %s then.
* Remove unanimous MAM displayMichael Vetter2020-04-257-59/+18
| | | | | | For some time users could choose to have the old way "unanimous" where all the MUC history is just grey (or whatever was set). Now it is always just displayed like regular new incoming MUC text.
* Mention the related commands for /correct and /correctionWilliam Wennerström2020-04-241-3/+5
|
* ui: fix conditionDmitry Podgorny2020-04-232-2/+4
| | | | | Fix mistake in a condition. Also add sanity check to win_refresh_with_subwin().
* Fixup for bad56b50623837644d0888cf8e5b059111b65ac2Michael Vetter2020-04-221-1/+1
| | | | sorry.. doing too many things at once..
* wins_show_subwin(): Add windows type testMichael Vetter2020-04-221-0/+6
| | | | Fix https://github.com/profanity-im/profanity/issues/1321
* _handle_carbons(): fix potential memleakMichael Vetter2020-04-211-2/+4
|
* inp_readline() Correct slashguard featureMichael Vetter2020-04-211-4/+6
| | | | Protect against invalid reads by checking the length.
* Make compiler happy about win_refresh_without_subwinMichael Vetter2020-04-201-1/+1
|
* win_refresh_with_subwin() fixupMichael Vetter2020-04-201-2/+1
| | | | Fixup for 86af6925d9fc0b2656eac15b0c8c7aba60589ce5
* _iq_id_handler_free() dont set NULLMichael Vetter2020-04-201-1/+0
| | | | No effect here.
* Remove unused func wins_close_current()Michael Vetter2020-04-202-7/+0
|
* Remove file_getline() declarationMichael Vetter2020-04-201-1/+0
| | | | Follow up for a6fa8e8e0d6b86c669ac2fb2b7be44812604c21f
* _destroy_tab() dont set tab to NULLMichael Vetter2020-04-201-1/+0
| | | | | | | Setting the local pointer to NULL has no effect. _destroy_tab() is used for g_hash_table_new_full() so we cant use a ** and set tab to NULL.
* Simplify win_refresh_with_subwin()Michael Vetter2020-04-201-6/+5
|
* _mucwin_print_mention(): No need to assign posMichael Vetter2020-04-201-1/+1
|
* ui_room_join() dont get nick twiceMichael Vetter2020-04-201-1/+0
|
* cons_show_aliases() simpify conditionMichael Vetter2020-04-201-3/+1
|
* Fix parsing of alias commandMichael Vetter2020-04-201-1/+1
| | | | | This actually only set the local ran pointer to NULL. But we want an effect on the outside variable.
* log: don't log dtMichael Vetter2020-04-201-3/+3
| | | | Use another name.
* log: Dont shadow logpMichael Vetter2020-04-201-16/+16
| | | | Let's use another name.
* Remove unneeded file_getline()Michael Vetter2020-04-201-44/+0
| | | | Not needed anymore since 0942d98c6116dc4b9b608e7483f1d6a8f62c84d7
* Fix potential memleak in stanza_create_caps_from_query_element()Michael Vetter2020-04-201-4/+12
| | | | | Each of those should only occur one time. But let's make sure we only write/alloc one time to be on the safe side.
* Make _inp_edited() more robustDmitry Podgorny2020-04-191-1/+8
|
* Merge pull request #1318 from DebXWoody/OMEMO-MUC-DeviceMichael Vetter2020-04-181-4/+6
|\ | | | | OMEMO Device List only for non anonymous MUCs
| * OMEMO Device List only for non anonymous MUCsDebXWoody2020-04-171-4/+6
| | | | | | | | | | | | | | Profanity request the OMEMO Device List for all members, also if the MUC is anonymouse. If the user is Admin / Owner, the device list will be requtest. Issue #1315
* | Escape message before adding to SQL backendMichael Vetter2020-04-181-1/+5
|/
* Define lock in profanity.h as externMichael Vetter2020-04-172-1/+2
| | | | Fix https://github.com/profanity-im/profanity/issues/1314
* Don't expose upload_processesMichael Vetter2020-04-174-12/+27
| | | | | | | | That's actually not good practise. Realized this when checking for multiple symbol definition in issue mentioned below. Regards https://github.com/profanity-im/profanity/issues/1314
* Review logging in iq.cMichael Vetter2020-04-141-27/+39
|
* Review logging for blocking.cMichael Vetter2020-04-141-2/+2
|
* Review logging in presence.cMichael Vetter2020-04-141-5/+4
| | | | | Some stuff just floods the log file. We only need this when debugging. Others are useless without more info.
* Free GError objectsDmitry Podgorny2020-04-142-2/+5
| | | | | | | | | | glib functions can allocate a GError object that must be freed with g_error_free(). Otherwise a memory leak happens. There are similar unfixed places in omemo, check: grep "&error" src/omemo/omemo.c Fixes #1304.
* Only print chathistory if regular chat messageMichael Vetter2020-04-131-1/+4
| | | | | | | | | | | MUCPMs and regular chat messages get printed with the same code. But we don't save MUC PMs in the sqldb, because another jid could use the same nick the next time. And if we would take the log out we would need a different routine, checking for resourcepart too. Fix https://github.com/profanity-im/profanity/issues/1312
* Free timestamp correctlyMichael Vetter2020-04-131-2/+3
| | | | g_date_time_add_days() actually creates a new one.
* Add hidden MAM setting and trigger MAM retrievel when opening new windowMichael Vetter2020-04-123-8/+17
| | | | | | | | | | | | Only when we start the conversation. Not yet when we get messaged and a new window is opened. Need to have sorting of messages in the window buffer then, I guess. Also MAM IQ should only be send one time in such a case. If MAM is enabled history from sql backend will not be shown. `mam` in profrc enables experimental MAM. Can change soon again. Don't rely on stuff in this stage ;)
* Check if server suppors MAMMichael Vetter2020-04-122-2/+6
|
* Get MAM since yesterdayMichael Vetter2020-04-121-1/+7
| | | | | | | | | | | | | Later we will have several options. Getting everything since last timestamp (if none everything at all). Getting everything since today + configure time (1 week). Should also have a reload all command like conversations once you cleared the history. All MAM messages should be written into sql db. And then probably displayed from there so that regular history works too.
* MAM: Correctly display incoming MAM chat messageMichael Vetter2020-04-114-15/+42
|
* Add to_jid field to ProfMessage structMichael Vetter2020-04-119-91/+103
| | | | | Is usefult in many cases if we want cleaner code. Hope this edit didn't break anything though ;-)
* Quick and dirty display of MAM messagesMichael Vetter2020-04-111-3/+6
|
* First test with receiving MAMMichael Vetter2020-04-111-0/+27
|
* _handle_chat: return if no 'from'Michael Vetter2020-04-111-0/+3
| | | | Let's not crash :-)
* Don't crash if we get a message without from or typeMichael Vetter2020-04-111-1/+8
| | | | | | | | MAM messages don't have a type nor a from. If we detect a message without type let's log it and exit without continuing to try to parse it. Otherwise we go into _handle_chat() and crash on the no from.
* First MAM testMichael Vetter2020-04-114-0/+105
| | | | | | Send a request (which we can't handle yet) :-) Regards https://github.com/profanity-im/profanity/issues/660
* Fix memory leaks in cons_roster_setting()Dmitry Podgorny2020-04-101-0/+3
|
* Fix error in getting previous chatlogMichael Vetter2020-04-101-1/+5
| | | | | | | | | Our search was too broad, and thus incorrect. One of the various mistakes it can cause was https://github.com/profanity-im/profanity/issues/1308 Fix https://github.com/profanity-im/profanity/issues/1308
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-18 15:43:31 +0000