| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
Fixes potential memory leak too.
|
| |
|
|
|
|
| |
Use `main.trackbar` in themes.
|
|
|
|
|
| |
Fix bug introduced in 1f8b1eb740391941e79e1004ad041f8178a2b674.
Forgot to strdup() here.
|
|
|
|
| |
Fix https://github.com/profanity-im/profanity/issues/1264
|
| |
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
_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.
|
| |
|
|
|
|
| |
We will need this if we want to display the Name instead of the JID.
|
|
|
|
|
|
| |
So far we printed one after the last received message, which doesn't
make much sense of course.
Now only print one if there is not already one present.
|
|
|
|
|
|
|
|
| |
Use the whole line.
We do this in win_redraw() so upon terminal size change it still
matches.
Regards https://github.com/profanity-im/profanity/issues/1238
|
|
|
|
|
|
|
|
| |
Print dashes on the position we last left off in a chat window.
So far the number of dashes is hardcoded, and the feature only works in
chat windows.
Regards https://github.com/profanity-im/profanity/issues/1238
|
|
|
|
|
|
| |
Implement settings for redgreen and blue blindness.
Regards https://github.com/profanity-im/profanity/issues/1191
|
|
|
|
|
|
|
|
|
| |
* add theme_hash_attrs()
* when printing a user message check PREF_COLOR_NICK to decide whether
to colorize it or not
ideally we should hash the jid instead of the nick but this is already
a first step.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is encountered when biboumi is used.
Example: `/join #debian-next%irc.oftc.net@biboumi.lebihan.pl`
It seems then time can be null.
g_date_time_format() will not work in this case although time_pref will
not be "off". So let's not call g_date_time_format() in this case. But
treat it like time is set to off.
However message reflection will not work properly with biboumi.
Probably we dont get origin-id.
Fix https://github.com/profanity-im/profanity/issues/1230
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
XEP-0184: Message Delivery Receipts, *requires* the id attribute.
Generally this is not the case.
For this reason the id was only present in the DeliveryReceipt struct
since it was only used for XEP-0184.
For https://github.com/profanity-im/profanity/issues/660 XEP-0313 MAM
and https://github.com/profanity-im/profanity/issues/805 XEP-0308 Last Message Correction
we will also need the id.
So in preparation for further work let's move the id to the general
ProfBuffEntry.
We will need to adapt code so that we actually always write the ID if we
receive one.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For OMEMO we had a list with our sent messages.
It was used so that we don't decrypt our own messages in MUCs that come
in via reflection.
Recently for https://github.com/profanity-im/profanity/pull/1209 we
started to use origin-id and use an algorithm so we can detect our own
sent messages via checking origin-id.
Profanity uses the same id for the message ID and origin-id.
With 06f300a42c4c627b6f1817bd48d92f083ffd9883 we added the
message_is_sent_by_us() function.
We implemented XEP-0359 this way to fix
https://github.com/profanity-im/profanity/issues/1201 so that we don't
log our own messages in MUCs twice.
We can now check whether the message was sent by us using this function
and can get rid of the list.
Probably we could also put many parts of the sv_ev_room_message()
function inside (else) part of `if (!(g_strcmp0(mynick,
message->jid->resourcepart) == 0 && message_is_sent_by_us(message))) {`.
Have to look more closely whether any of this needs to be run in case
the message actually comes from us.
|
|\
| |
| | |
Change /clear behaviour. Closes issue #855.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
History was always printed with `THEME_DEFAULT` we now use
`THEME_TEXT_HISTORY` which is accesible in theme files via
`main.text.history`.
Fix https://github.com/profanity-im/profanity/issues/1170
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
Probably missing copy of body to plain in carbon and privmessage.
Only covers the incoming message path because goal is OMEMO decryption
of untrusted message.
Cover some of the log functions but not all.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Reflected messages can't be filtered by nick only otherwise you might
ignore messages comming from you on another devices.
Consequently we maintain a list of sent messages id in mucwin.
To be sure the id will be correctly reflected we use the origin-id
stanza.
|
| | |
|
| | |
|
| |
| |
| |
| | |
Also store identity keys into account
|
| | |
|
| | |
|