| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
No need to continue to loop through the rest.
|
|
|
|
|
|
|
| |
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()
|
|
|
|
| |
We need to unref the temp datetimes again.
|
|
|
|
| |
We need to unref the timestamp before setting a new one.
|
|
|
|
| |
Could be that args[1] is not set.
|
|
|
|
| |
Fixes potential memory leak too.
|
|
|
|
| |
Some instructions were missing whitespace or punctuation.
|
| |
|
|
|
|
| |
Make clear that result should never be freed.
|
|
|
|
|
| |
`profanity -f TEST` will use `~/.local/share/profanity/logs/TEST.log` as
the log file.
|
| |
|
|
|
|
| |
Use `main.trackbar` in themes.
|
|
|
|
|
|
|
|
| |
We use the same incoming function as for regular incoming text here. But
don't want to filter out our own messages since we didn't print them
during sending.
Follow up to 8ee2cdadc88978ea26e6b6eb56f2aaa1fd5a81df
|
| |
|
| |
|
|
|
|
| |
Dont duplicate code.
|
|
|
|
|
| |
Fix bug introduced in 1f8b1eb740391941e79e1004ad041f8178a2b674.
Forgot to strdup() here.
|
| |
|
|
|
|
| |
Fix https://github.com/profanity-im/profanity/issues/1264
|
|
|
|
| |
Copy paste error. We actually set the omemo char..
|
|
|
|
| |
Fix https://github.com/profanity-im/profanity/issues/1261
|
|
|
|
|
|
| |
So we can use it somewhere else too.
Regards https://github.com/profanity-im/profanity/issues/1261
|
|
|
|
|
|
|
|
|
| |
`/logging group color` has:
* `unanimous` which will color it with one unanimous color. Like it was
done always.
* `regular` which colors it like regular incoming messages.
Regards https://github.com/profanity-im/profanity/issues/1261
|
|
|
|
| |
Just pass ProfMessage.
|
| |
|
|\
| |
| | |
Add builds.sr.ht CI for OpenBSD
|
| |
| |
| |
| |
| |
| |
| |
| | |
* Add .builds/openbsd.yml for builds.sr.ht
* Update travis-build.sh -> ci-build.sh with OpenBSD case
* Fix libdl check in configure.ac (OpenBSD has libdl built-in)
* Fix some minor issues found when compiling on OpenBSD with GCC (e.g.
uninitialized variables)
|
| |
| |
| |
| |
| |
| |
| | |
We decrypt both 12 and 16 bytes.
And send 12 instead of 16 bytes now.
Close https://github.com/profanity-im/profanity/issues/1272
|
| |
| |
| |
| | |
We never use the printf like behaviour anyways.
|
| |
| |
| |
| | |
We never use the printf like behaviour anyways.
|
| |
| |
| |
| | |
We never use the printf like behaviour anyways.
|
| |
| |
| |
| | |
We never use the printf like behaviour anyways.
|
| | |
|
| |
| |
| |
| | |
Regards https://github.com/profanity-im/profanity/pull/1270
|
| |
| |
| |
| |
| |
| | |
`/pgp sendfile on` allows unencrypted file transfer in an PGP session.
Regards https://github.com/profanity-im/profanity/pull/1270
|
| |
| |
| |
| |
| |
| | |
`/otr sendfile on` allows unencrypted file transfer in an OMEMO session.
Regards https://github.com/profanity-im/profanity/pull/1270
|
| |
| |
| |
| |
| |
| |
| | |
`/omemo sendfile on` allows unencrypted file transfer in an OMEMO
session.
Regards https://github.com/profanity-im/profanity/pull/1270
|
|/ |
|
|
|
|
| |
Regards https://github.com/profanity-im/profanity/issues/1265
|
| |
|
| |
|
| |
|
|
|
|
|
| |
We need to change the buffer structure first, so that we save the from
field there.
|
| |
|
|
|
|
|
|
|
| |
If we are connected with another client and send a message, then correct
it. We now display it correctly in Profanity.
Id wasn't saved for carbon copied messages too so far.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
So far receipts are only send if we have enabled it and the other client
supports it.
But it could be that the other person is connected with several clients.
One supporting it and the other which doesn't. If the not supporting one
is active and we send to a fulljid, then we won't get receipts.
Probably it's best to just always send them if they are enabled in
Profanity. And not try to find out the capabilities of the other client.
Fix https://github.com/profanity-im/profanity/issues/1268
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
In aa3693daa211b36c78d136d5a1ee9f3258e21352 I renamed
`win_println_me_message()` -> `win_print_outgoing_muc_msg()`.
Now: `win_println_them_message()` -> `win_println_incoming_muc_msg()`
to be more consistent and descriptive.
|