| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| |
| |
| |
| |
| | |
Maybe if we only use `/connect` we dont have ProfAccount. In that case
we won't log anything. Only if a account is used we log.
If this is the case or the init of the db didn't work we still want
profanity to run but wont log anything to the db.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Timestamps are only set if a message is delayed.
If none is set let's set it upon recaival so we don't have to set it
when it gets displayed.
This means we will also have it for logs etc in the ProfMessage.
|
| |
| |
| |
| | |
First trial. Not covering all cases yet.
|
| | |
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
| |
I plan to save all messages in an SQLite db.
For retrieving information it's nicer than having it in a text file.
We will have more info in there and easier to parse it.
This will also be good for later MAM
(https://github.com/profanity-im/profanity/issues/660).
Regular text files will still be an option for users so that they can
easily grep them and do whatever they like.
Internally Profanity will only use the SQLite db.
|
|\
| |
| | |
Fix few memory leaks
|
| |
| |
| |
| |
| | |
There are multiple paths which lead to rosterwin_roster(). The function
doesn't free list returned by wins_get_private_chats().
|
|/ |
|
|\
| |
| | |
Fix few memory leaks
|
| |
| |
| |
| |
| |
| | |
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.
|
|/ |
|
| |
|
|
|
|
|
| |
Many people seem to miss because they check only github and not the
website.
|
| |
|
|\
| |
| | |
Fixed memory leak in ProfMucWin
|
| |
| |
| |
| |
| | |
Profanity remembers last message and its id for the message correction
feature. We must free them in window destructor.
|
| | |
|
| | |
|
| | |
|
|\| |
|
| |\
| | |
| | | |
Fallback for nproc for systems without GNU coreutils
|
| |/ |
|
| | |
|
|/
|
|
|
| |
Don't return too early. We still need to check for regular omemo
autocompletion (omemo_ac).
|
|\
| |
| | |
Use latest Docker in CI
|
|/
|
|
|
|
| |
Force a Docker upgrade for all Linux runners.
Fixes: #1294
|
|
|
|
| |
Regards https://github.com/profanity-im/profanity/issues/1294
|
| |
|
|
|
|
| |
https://github.com/profanity-im/profanity/issues/1294
|
|
|
|
| |
Regards https://github.com/profanity-im/profanity/issues/1294
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
| |
Tests fail in TW image. Doesn't seem our fault.
Let's try to find out since when.
|
|
|
|
| |
This was forgotten in f13168005512fe4219741d9daf83681dd9ed3d63.
|
|\
| |
| | |
Fix memory leak of presence object
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
`profanity -t bios` loads the bios theme now.
Fix https://github.com/profanity-im/profanity/issues/1286
|
| |
|
|
|
|
|
|
| |
`/titlebar use name|jid` -> `/titlebar show|hide name|jid`
Fix https://github.com/profanity-im/profanity/issues/1284
|
| |
|