| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
|
|
|
| |
I suspect this was just a copy paste error.
`_win_create_simple_layout()` is called in other creation functions like
`win_create_config()` or `win_create_private()`.
I suspect when `win_create_muc()` was created it was just copied. But in
this function we actually set the layout ourself later.
So calling the function isn't needed.
Regards https://github.com/profanity-im/profanity/issues/1279
|
|
|
|
| |
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()
|
|
|
|
| |
Fixes potential memory leak too.
|
| |
|
|
|
|
| |
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
|
|
|
|
|
| |
Fix bug introduced in 1f8b1eb740391941e79e1004ad041f8178a2b674.
Forgot to strdup() here.
|
|
|
|
| |
Fix https://github.com/profanity-im/profanity/issues/1264
|
|
|
|
| |
Fix 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 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.
|
| |
| |
| |
| |
| |
| | |
`/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
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
No `/correct` allowed in privwins
|
|
|
|
| |
Outgoing `/correct` will still work.
|
|
|
|
|
|
| |
Including OMEMO encrypted ones.
Also rename `win_println_me_message()` to `win_print_outgoing_muc_msg()
as I think it's a more descriptive name.
|
|
|
|
|
| |
People could change messages of other people if the nick isn't
registered.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
_win_print() and _win_printf() sound like they are the same. But
actually they are something totally different.
I renamed _win_print() to _win_print_internal() for that reason. It's
more about actually drawing to the ncurses window.
_win_printf() calls _win_print() and also writes the text to the window
buffer. Which _win_print() didn't, it was really just the ncurses
specific things.
In some cases there is _win_print_internal() called after a
buffer_append() in those cases it might be more correct to actually call
_win_printf().
It was not done so far. But probably is better. But will mean a bit more
operations.
I'll have to check this later.
|
|
|
|
| |
and make it static.
|
|
|
|
|
| |
So far we don't do this for encrypted messages. Still needs to be done.
And MUC also needs to be done.
|
|
|
|
|
|
|
|
| |
So far the correction is sent. But the UI in Profanity itself is not
updated.
Also autocompletion for `/correct` with the last sent message is
missing.
|
|
|
|
| |
and print settings if only `/correction` is run.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
I think both the window and the buffer should also be cleared in case
`/clear` is issue and persist_history is off.
Otherwise it could happen that win_redraw() redraws the whole content of
the buffer again.
|
|
|
|
|
| |
Actually presence_colour should be stopped there.
Thanks to rumin-miller for finding this.
|
|
|
|
| |
Fix #1068
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
So far when loading a theme it also overwrote the preferences the user
set.
Lengthy discussion can be found at
https://github.com/profanity-im/profanity/issues/1077
Now we use `/theme load themename` to load the [colours] part of a
themem only.
`/theme full-load themename` will load the complete theme including
preferences set in there.
Regards https://github.com/profanity-im/profanity/issues/1077
|
|
|
|
|
| |
`/os on|off` now let's one choose whether to include the OS name once
`/software` (XEP-0092) is ran on us.
|
| |
|
|
|
|
| |
Use helper function for duplicate code.
|
|
|
|
| |
Add `/titlebar use [name|jid]`.
|
| |
|