about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* Fix multiple memory leaks related to rosterwin_roster()Dmitry Podgorny2020-04-061-0/+1
| | | | | There are multiple paths which lead to rosterwin_roster(). The function doesn't free list returned by wins_get_private_chats().
* Fix memory leak in cons_show_disco_info()Dmitry Podgorny2020-04-061-1/+1
|
* Merge pull request #1298 from profanity-im/memleaksMichael Vetter2020-04-052-0/+2
|\ | | | | Fix few memory leaks
| * Fix memory leak in stanza_attach_correction()Dmitry Podgorny2020-04-051-0/+1
| | | | | | | | | | | | xmpp_stanza_add_child() takes own reference to the child stanza. Therefore we have to release our reference or the child is lost and not freed otherwise.
| * Fix memory leak in _rosterwin_resources()Dmitry Podgorny2020-04-051-0/+1
|/
* readme: add repos and urlsMichael Vetter2020-04-051-2/+2
|
* Add blog to readmeMichael Vetter2020-04-051-0/+2
| | | | | Many people seem to miss because they check only github and not the website.
* Dont have account otr setting if built without otrMichael Vetter2020-04-031-0/+2
|
* Merge pull request #1297 from profanity-im/memleak-mucwinMichael Vetter2020-04-031-0/+2
|\ | | | | Fixed memory leak in ProfMucWin
| * Fixed memory leak in ProfMucWinDmitry Podgorny2020-04-031-0/+2
| | | | | | | | | | Profanity remembers last message and its id for the message correction feature. We must free them in window destructor.
* | Dont have otr autocompletion if build without otr supportMichael Vetter2020-04-031-0/+16
| |
* | Dont have pgp autocompletion if build without pgp supportMichael Vetter2020-04-031-2/+16
| |
* | Dont even create OMEMO ac vars if we build without supportMichael Vetter2020-04-031-0/+10
| |
* | Merge branch 'master' of github.com:profanity-im/profanityMichael Vetter2020-04-021-1/+12
|\|
| * Merge pull request #1296 from wstrm/ci-without-coreutilsMichael Vetter2020-04-011-1/+12
| |\ | | | | | | Fallback for nproc for systems without GNU coreutils
| | * Fallback for nproc for systems without GNU coreutilsWilliam Wennerström2020-04-011-1/+12
| |/
* | 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.