| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
There is actually no reason to get the window number here.
|
| |
|
|
|
| |
Part of what `roster_update()` does manually is actually done in
`roster_change_name()`.
|
| | |
|
| |
|
|
|
|
|
|
| |
Double-check that a <delay/> tag on a groupchat message was actually
added by the MUC service (rather than the sending client) before
assuming it was received from the MUC history.
Fixes #1173.
|
| |\
| |
| | |
Possibility to specify alternative config file
|
| | |
| |
| |
| | |
Introduce `profanity -c` to specify an alternative config file.
|
| |/
|
|
|
| |
We don't need to do all the timing stuff if last activity is disabled
anyways.
|
| |\
| |
| | |
Don't print subscribed message if contact is already in roster
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This occured with a user running Cisco Jabber. It seems this server
sends repeated presence subscribed stanzas. And although I find this
strange according to RFC this seems to be ok.
So let's filter them and only display in the console output and to the
log. But don't open seperate windows.
Fix https://github.com/profanity-im/profanity/issues/1165
|
| |/
|
|
|
|
|
| |
Most applications have an 'apply changes' button. This makes testing
easier too.
Implement https://github.com/profanity-im/profanity/issues/1164
|
| |\
| |
| | |
Fix memleak in /cmd exec
|
| | | |
|
| |\ \
| |/
|/| |
Fix memleaks in OMEMO
|
| | |
| |
| |
| | |
I don't see a reason for strdupping here.
|
| | | |
|
| | |
| |
| |
| | |
I don't see a reason for strdupping here.
|
| |/
|
|
|
| |
Command form userdata were freed by iq_id_handler.
We should now free the command ourself.
|
| | |
|
| |\
| |
| | |
Fix segfault in group add/remove command
|
| | |
| |
| |
| |
| | |
Also regarding destructor.
Fix https://github.com/profanity-im/profanity/issues/1159
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Exiting without freeing in some cases.
|
| | |
| |
| |
| | |
strdup() is not needed here but will actually lead to a memleak.
|
| | |
| |
| |
| | |
current_name should not be const and should be freed.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
This should actually never happen because we have the mechanism that
checks the commands. But let's do it in case we break something in that
mechanism and to make clang happy.
Fixes clangs: 'Argument with 'nonnull' attribute passed null'
|
| | | |
|
| |\ \
| |/
|/| |
Always check for directory changes with sendfile auto completion
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Instead of only checking for files when 'last_directory' has changed, do
it every time.
Add autocomplete_update function that updates the items while retaining
last_found and search_str.
Fixes #1099
|
| | |
| |
| |
| |
| |
| | |
Another case of double free() due to new destructor.
Fixes https://github.com/profanity-im/profanity/issues/1156
|
| | | |
|
| | |
| |
| |
| | |
Taken care of by the destructor.
|
| | |
| |
| |
| | |
Test for correct number of arguments before using argument.
|
| |\ \
| | |
| | |
| | |
| | | |
Hotfix/omemo memleaks
Regards https://github.com/profanity-im/profanity/issues/1131
|
| | | | |
|
| | | | |
|
| | | | |
|
| |/ /
| |
| |
| | |
Regards https://github.com/profanity-im/profanity/issues/1148
|
| | | |
|
| | |
| |
| |
| |
| | |
Let's use calloc instead of malloc and then setting almost all fields to
NULL.
|
| | |
| |
| |
| | |
This is taken care of now in the destructor _pendingPresence_free().
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fix:
```
==18682== 408 bytes in 17 blocks are definitely lost in loss record
3,279 of 3,632
==18682== at 0x483677F: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==18682== by 0x42F602: roster_update_presence (roster_list.c:129)
==18682== by 0x448AA3: sv_ev_contact_online (server_events.c:906)
==18682== by 0x43D2BA: _available_handler (presence.c:674)
==18682== by 0x43C81B: _presence_handler (presence.c:398)
==18682== by 0x5AF118E: handler_fire_stanza (handler.c:124)
==18682== by 0x5AEDBDA: _handle_stream_stanza (conn.c:1253)
==18682== by 0x5AFA43E: _end_element (parser_expat.c:190)
==18682== by 0x6818AA4: doContent (xmlparse.c:2977)
==18682== by 0x681A3AB: contentProcessor (xmlparse.c:2552)
==18682== by 0x681D7EB: XML_ParseBuffer (xmlparse.c:1988)
==18682== by 0x681D7EB: XML_ParseBuffer (xmlparse.c:1957)
==18682== by 0x5AF0A63: xmpp_run_once (event.c:255)
==18682== by 0x432E5D: connection_check_events (connection.c:104)
==18682== by 0x4323B3: session_process_events (session.c:255)
==18682== by 0x42C097: prof_run (profanity.c:128)
==18682== by 0x4B25B9: main (main.c:172)
```
|
| | |
| |
| |
| |
| | |
Free is done in destructor now.
Regards https://github.com/profanity-im/profanity/issues/1148
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
omemo_key_free() was called to free the key.
It free the key->data too. But in same cases this was not set yet. So
we need to set the data to NULL (or use calloc) at initialization so
that omemo_key_free() only frees it if it was actually allocated.
Regards https://github.com/profanity-im/profanity/issues/1148
|