| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|
|
|
| |
Start https://github.com/profanity-im/profanity/issues/1340
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
Fix mistake in a condition. Also add sanity check to
win_refresh_with_subwin().
|
|
|
|
| |
sorry.. doing too many things at once..
|
|
|
|
| |
Fix https://github.com/profanity-im/profanity/issues/1321
|
|
|
|
| |
Protect against invalid reads by checking the length.
|
| |
|
|
|
|
| |
Fixup for 86af6925d9fc0b2656eac15b0c8c7aba60589ce5
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
| |
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 ;)
|
| |
|
|
|
|
|
| |
Is usefult in many cases if we want cleaner code.
Hope this edit didn't break anything though ;-)
|
| |
|
| |
|
| |
|
|
|
|
| |
So we don't have to check for MUC another way.
|
| |
|
|
|
|
| |
Same behaviour like when we used to get it from the text files.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
We now dont get the log files from the text files via chat_log_get_previous() anymore.
We use the sql backend via log_database_get_previous_chat().
So far it just has the same behaviour like chat_log_get_previous(),
except that in _chatwin_history() we don't pass the sender to
win_print_history() which should be fixed in a commit soon.
And log_database_get_previous_chat() can later easily be expanded to fix
https://github.com/profanity-im/profanity/issues/205.
|
| |
|
|
|
|
|
| |
There are multiple paths which lead to rosterwin_roster(). The function
doesn't free list returned by wins_get_private_chats().
|
| |
|
| |
|
|
|
|
|
| |
Profanity remembers last message and its id for the message correction
feature. We must free them in window destructor.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
`/titlebar use name|jid` -> `/titlebar show|hide name|jid`
Fix https://github.com/profanity-im/profanity/issues/1284
|
| |
|
|
|
|
|
| |
New command `/slashguard` tries to protect against typing ` /quit` by
not allowing a slash in the first 4 characters.
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
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`.
|
| |
|
| |
|
|
|
|
| |
Not all cases covered yet.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|