about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
...
* | Only have OMEMO autocompletion if we build with OEMO supportMichael Vetter2020-04-021-2/+6
| |
* | Fix omemo autocompletion mitakeMichael Vetter2020-04-021-2/+0
|/ | | | | Don't return too early. We still need to check for regular omemo autocompletion (omemo_ac).
* Merge pull request #1295 from wstrm/upgrade-dockerMichael Vetter2020-03-303-7/+10
|\ | | | | Use latest Docker in CI
| * Use latest Docker in CIWilliam Wennerström2020-03-303-7/+10
|/ | | | | | Force a Docker upgrade for all Linux runners. Fixes: #1294
* thanks travis..Michael Vetter2020-03-302-3/+5
| | | | Regards https://github.com/profanity-im/profanity/issues/1294
* travis: use bionicMichael Vetter2020-03-301-0/+1
|
* Next travis tryMichael Vetter2020-03-301-1/+1
| | | | https://github.com/profanity-im/profanity/issues/1294
* Another try at dockerMichael Vetter2020-03-301-1/+1
| | | | Regards https://github.com/profanity-im/profanity/issues/1294
* Run docker in privileged modeMichael Vetter2020-03-301-1/+1
| | | | | | | | | | | | | From https://docs.docker.com/engine/reference/run/: ``` When the operator executes docker run --privileged, Docker will enable access to all devices on the host as well as set some configuration in AppArmor or SELinux to allow the container nearly all the same access to the host as processes running outside containers on the host. ``` Regards https://github.com/profanity-im/profanity/issues/1294
* os TW 20200325 testMichael Vetter2020-03-301-1/+1
|
* Test oS TW 20200324Michael Vetter2020-03-301-1/+1
| | | | | Tests fail in TW image. Doesn't seem our fault. Let's try to find out since when.
* Remove 'use' from titlebar autocompletionMichael Vetter2020-03-291-1/+0
| | | | This was forgotten in f13168005512fe4219741d9daf83681dd9ed3d63.
* Merge pull request #1292 from profanity-im/memleak-issue1279Michael Vetter2020-03-291-0/+2
|\ | | | | Fix memory leak of presence object
| * Fix memory leak of presence objectDmitry Podgorny2020-02-231-0/+2
|/ | | | | | | | | | | | | | | | | | | | | | | | | The memory leak happens when a presence is received for a MUC room. The JID is not present in the roster, so updating its status is ignored. We have to free resource in this case, because it has no owner and is lost otherwise. ==25736== 47 (32 direct, 15 indirect) bytes in 1 blocks are definitely lost in loss record 1,625 of 3,399 ==25736== at 0x4A330FF: malloc (vg_replace_malloc.c:309) ==25736== by 0x13A962: resource_new (resource.c:47) ==25736== by 0x145501: _available_handler (presence.c:665) ==25736== by 0x145501: _presence_handler (presence.c:399) ==25736== by 0x145501: _presence_handler (presence.c:358) ==25736== by 0x80D5F34: handler_fire_stanza (in /usr/lib64/libstrophe.so.0.0.0) ==25736== by 0x80D2B49: _handle_stream_stanza (in /usr/lib64/libstrophe.so.0.0.0) ==25736== by 0x80E15CE: _end_element (in /usr/lib64/libstrophe.so.0.0.0) ==25736== by 0x843EE9B: doContent (in /usr/lib64/libexpat.so.1.6.10) ==25736== by 0x843F94B: contentProcessor (in /usr/lib64/libexpat.so.1.6.10) ==25736== by 0x8441E77: XML_ParseBuffer (in /usr/lib64/libexpat.so.1.6.10) ==25736== by 0x80D586B: xmpp_run_once (in /usr/lib64/libstrophe.so.0.0.0) ==25736== by 0x13E07E: connection_check_events (connection.c:119) ==25736== by 0x13869C: prof_run (profanity.c:129) Fixes #1279.
* Fix edit mistakeMichael Vetter2020-03-271-1/+1
|
* Upgrade examplesMichael Vetter2020-03-261-39/+39
|
* Add jubalian themeMichael Vetter2020-03-251-0/+166
|
* Add history.muc.color to theme templateMichael Vetter2020-03-251-0/+1
|
* Add setting to not colorize own nick according to xep-0392Michael Vetter2020-03-257-5/+31
| | | | | | | | | | | | | | | | | | Some users might want there nick to always stay white (etc) for easier recognition. Now we can do `/color own off` to not generate the color based on xep-0392. The `me=` color (etc) from the theme will then be used. Once we run this command `theme_load()` is called again. And the theme looks totally wrong. We encountered this at other times already and I think it's nothing wrong with this new code here now but that there seems to be a missing closing attr for the color when drawing. Should be investigated seperately. Fix https://github.com/profanity-im/profanity/issues/1288
* Add -t theme optionMichael Vetter2020-03-244-11/+27
| | | | | | `profanity -t bios` loads the bios theme now. Fix https://github.com/profanity-im/profanity/issues/1286
* Fix old typo in titlebar presenceMichael Vetter2020-03-241-1/+1
|
* titlebar: allow displaying MUC name and MUC jidMichael Vetter2020-03-249-63/+65
| | | | | | `/titlebar use name|jid` -> `/titlebar show|hide name|jid` Fix https://github.com/profanity-im/profanity/issues/1284
* move titlebar code in correct functionMichael Vetter2020-03-242-20/+10
|
* Add slashguard featureMichael Vetter2020-03-1810-1/+54
| | | | | New command `/slashguard` tries to protect against typing ` /quit` by not allowing a slash in the first 4 characters.
* Enable popular features by defaultMichael Vetter2020-03-171-0/+5
| | | | | | | Most clients have them enabled by default already for a smoother modern XMPP experience. Enable by default: allowing message corrections, sending of read receipts, enabling carbons, typing/chat states.
* Add note about 256 color supportMichael Vetter2020-03-171-1/+2
|
* Add cons_avatar_setting to unit test stubMichael Vetter2020-03-101-0/+1
|
* xep-0084/avatar: add option to open avatar directlyMichael Vetter2020-03-109-9/+88
| | | | | | | | | | | Change: `/avatar me@somewhere.org` -> `/avatar get me@somewhere.org` New: `/avatar cmd feh` `/avatar open me@somewhere.org` Implement https://github.com/profanity-im/profanity/issues/1281
* Make statusbar tab more resilientMichael Vetter2020-03-091-4/+8
| | | | | | | | If users input strange stuff and we can't create a jid from it even the setting is set to 'user' we still should fallback to the regular identifer. For example with `/msg @name%matrix.domain.org@matrix.org hi`.
* Merge branch 'buffer-from'Michael Vetter2020-03-094-31/+41
|\ | | | | | | | | | | | | Regards https://github.com/profanity-im/profanity/issues/805 Completes https://github.com/profanity-im/profanity/pull/1267 We now check who tries to "correct" a sent message.
| * Remove caution about LMCMichael Vetter2020-03-091-1/+1
| | | | | | | | We check the from now.
| * Rename ProfBufferEntry jid variableMichael Vetter2020-03-093-7/+7
| |
| * Check for sender of LMC messageMichael Vetter2020-03-091-11/+17
| |
| * Write from jid in bufferMichael Vetter2020-03-091-10/+13
| | | | | | | | Not all cases covered yet.
| * Add barejid to buffer structMichael Vetter2020-03-093-15/+16
|/
* Remove old commentsMichael Vetter2020-03-091-4/+0
|
* Use correct MUC message timestampMichael Vetter2020-03-092-5/+8
| | | | | | | | win_println_incoming_muc_msg() always used the current time. Now let's use whatever is sent int he message struct (from the delay stanza or the current time that we set now once the message is received). No playing with the time upon display anymore.
* Use ProfMessage as parameter for win_println_incoming_muc_msg()Michael Vetter2020-03-093-7/+6
|
* window.c: Rename variableMichael Vetter2020-03-091-3/+3
|
* Use proper OS names for OpenBSD and NetBSDMichael Vetter2020-03-091-2/+2
|
* Dont check before freeingMichael Vetter2020-02-271-8/+4
| | | | Regards d18ec23d0a38bd538d48f7e827fec0fceb9f230d
* Fix memory leak in win_create_muc()Michael Vetter2020-02-271-1/+0
| | | | | | | | | | | | | I suspect this was just a copy paste error. `_win_create_simple_layout()` is called in other creation functions like `win_create_config()` or `win_create_private()`. I suspect when `win_create_muc()` was created it was just copied. But in this function we actually set the layout ourself later. So calling the function isn't needed. Regards https://github.com/profanity-im/profanity/issues/1279
* Merge pull request #1278 from profanity-im/memleaksMichael Vetter2020-02-273-6/+31
|\ | | | | Fix few memory leaks
| * Fix few memory leaksDmitry Podgorny2020-02-273-6/+31
|/
* Set muc history correctly in _handle_groupchat()Michael Vetter2020-02-251-1/+1
| | | | Fix init. mistake introduced in e9c5c1979d836ed75c37d48651710b4fd125cfb2
* Free jid in muc_members_add()Michael Vetter2020-02-251-0/+1
| | | | Fix memleak.
* Stop buffer_remove_entry_by_id() once we found the entryMichael Vetter2020-02-251-0/+1
| | | | No need to continue to loop through the rest.
* Properly free buffer entryMichael Vetter2020-02-251-0/+1
| | | | | | | g_slist_delete_link() is not enough we also need to call _free_entry() on the entry. This fixes a memleak in win_insert_last_read_position_marker()
* Fix memleak in stanza_get_oldest_delayMichael Vetter2020-02-251-2/+14
| | | | We need to unref the temp datetimes again.
* Fix memleak in _handle_groupchat()Michael Vetter2020-02-251-1/+6
| | | | We need to unref the timestamp before setting a new one.