about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* Add hidden MAM setting and trigger MAM retrievel when opening new windowMichael Vetter2020-04-123-8/+17
| | | | | | | | | | | | 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 ;)
* Check if server suppors MAMMichael Vetter2020-04-122-2/+6
|
* Get MAM since yesterdayMichael Vetter2020-04-121-1/+7
| | | | | | | | | | | | | Later we will have several options. Getting everything since last timestamp (if none everything at all). Getting everything since today + configure time (1 week). Should also have a reload all command like conversations once you cleared the history. All MAM messages should be written into sql db. And then probably displayed from there so that regular history works too.
* MAM: Correctly display incoming MAM chat messageMichael Vetter2020-04-114-15/+42
|
* Add to_jid field to ProfMessage structMichael Vetter2020-04-119-91/+103
| | | | | Is usefult in many cases if we want cleaner code. Hope this edit didn't break anything though ;-)
* Quick and dirty display of MAM messagesMichael Vetter2020-04-111-3/+6
|
* First test with receiving MAMMichael Vetter2020-04-111-0/+27
|
* _handle_chat: return if no 'from'Michael Vetter2020-04-111-0/+3
| | | | Let's not crash :-)
* Don't crash if we get a message without from or typeMichael Vetter2020-04-111-1/+8
| | | | | | | | MAM messages don't have a type nor a from. If we detect a message without type let's log it and exit without continuing to try to parse it. Otherwise we go into _handle_chat() and crash on the no from.
* First MAM testMichael Vetter2020-04-114-0/+105
| | | | | | Send a request (which we can't handle yet) :-) Regards https://github.com/profanity-im/profanity/issues/660
* Merge pull request #1310 from profanity-im/memleaksMichael Vetter2020-04-101-0/+3
|\ | | | | Fix memory leaks in cons_roster_setting()
| * Fix memory leaks in cons_roster_setting()Dmitry Podgorny2020-04-101-0/+3
|/
* Fix error in getting previous chatlogMichael Vetter2020-04-101-1/+5
| | | | | | | | | Our search was too broad, and thus incorrect. One of the various mistakes it can cause was https://github.com/profanity-im/profanity/issues/1308 Fix https://github.com/profanity-im/profanity/issues/1308
* Merge pull request #1309 from profanity-im/use-after-freeMichael Vetter2020-04-101-4/+8
|\ | | | | Fix use-after-free in stanza_create_caps_from_query_element()
| * Fix use-after-free in stanza_create_caps_from_query_element()Dmitry Podgorny2020-04-091-4/+8
| | | | | | | | | | | | | | | | | | The function creates a form to find such strings as software, os, etc. It remembers the strings allocated by form_create() and use them below in caps_create(). The issue is that the form is destroyed before and as result the strings are freed too. As solution, allocate own copy of strings.
* | Merge pull request #1307 from profanity-im/memleaksMichael Vetter2020-04-091-0/+2
|\ \ | |/ |/| Fix memory leaks in _rosterwin_resources()
| * Fix memory leaks in _rosterwin_resources()Dmitry Podgorny2020-04-091-0/+2
|/
* Downgrade sqlite to 3.22.0Michael Vetter2020-04-081-2/+2
| | | | | | | Last version in Ubuntu LTS (bionic 18.04). I think we don't use later functionality. Let's see. glib version fits.
* Retrieve message type from databaseMichael Vetter2020-04-085-7/+21
| | | | So we don't have to check for MUC another way.
* Log after displaying the messageMichael Vetter2020-04-081-6/+6
| | | | | | | | Otherwise we print the freshly received message to the window twice. Once when receiving (and immediately printing), then logging it, and then again when we print the last 10 log entries. Fix https://github.com/profanity-im/profanity/issues/1305
* travis: enable osx againMichael Vetter2020-04-071-7/+7
| | | | | | | Seems like homebrew reverted their pkgconfig change for now. So finding gio should work again. Regards https://github.com/profanity-im/profanity/issues/1302
* Update dependencies in spec filesMichael Vetter2020-04-071-2/+6
|
* Update database stubMichael Vetter2020-04-071-3/+1
|
* Downgrade dependenciesMichael Vetter2020-04-072-6/+12
| | | | | | | | | | | Use g_date_time_format() instead of g_date_time_format_iso8601() to only rely on glib 2.56.0 which is the latest version in Debian Buster (current stable). We also only use basic sqlite functions so 3.27.0 should be fine there (also the one in Debian buster). Thanks to @DebXWoody.
* Require at least glib 2.62.Michael Vetter2020-04-061-2/+2
| | | | g_date_time_format_iso8601() is only in glib since 2.62.
* Add missing includesMichael Vetter2020-04-061-0/+3
|
* Require only sqlite 3.28.0Michael Vetter2020-04-061-2/+2
| | | | | We don't need newer features and so it runs on Leap 15.1 too. Let's see what Debian etc. need.
* Fix commentMichael Vetter2020-04-061-1/+1
|
* travis: disable osx buildMichael Vetter2020-04-061-7/+7
| | | | As long as brew has some problem: https://github.com/profanity-im/profanity/issues/1302
* Merge pull request #1282 from profanity-im/feature/sqlite-logMichael Vetter2020-04-0627-148/+578
|\ | | | | SQLite backend
| * Add hint about future ProfMessage Id needsMichael Vetter2020-04-061-0/+1
| |
| * Add comment what id is aboutMichael Vetter2020-04-061-0/+1
| |
| * db: actually display the last 10 entries in correct orderMichael Vetter2020-04-061-1/+1
| |
| * db: get last messages sorted by timestampMichael Vetter2020-04-061-1/+1
| |
| * db: Use type from message struct instead of having individual functionsMichael Vetter2020-04-063-85/+87
| |
| * Add type field to ProfMessageMichael Vetter2020-04-064-14/+27
| | | | | | | | The mucuser boolean is not now needed anymore.
| * db: Fix memleaksMichael Vetter2020-04-062-2/+2
| |
| * Add sql to error logMichael Vetter2020-04-061-2/+2
| | | | | | | | so we can more easily grep for it.
| * win_print_history() print 'me' on regular chats if we wrote the messageMichael Vetter2020-04-061-1/+9
| | | | | | | | Same behaviour like when we used to get it from the text files.
| * Adapt win_print_history() to work with muc tooMichael Vetter2020-04-065-24/+27
| |
| * Remove chat_log_get_previous()Michael Vetter2020-04-066-64/+6
| | | | | | | | | | | | | | | | | | | | | | | | 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.
| * Get regular chat history out of sql backendMichael Vetter2020-04-063-21/+53
| |
| * db: log encryption typeMichael Vetter2020-04-061-2/+19
| |
| * db: log "to" resourceMichael Vetter2020-04-061-8/+8
| |
| * db: log "from" resourceMichael Vetter2020-04-061-6/+7
| |
| * Fix copy paste errorMichael Vetter2020-04-061-1/+1
| |
| * Add log_database_add_*() test stubsMichael Vetter2020-04-061-1/+6
| |
| * Fix message_send_private unittest stubMichael Vetter2020-04-061-1/+6
| |
| * db: dont log reflected MUC messagesMichael Vetter2020-04-061-1/+1
| |
| * db: log all incoming and outgoing messagesMichael Vetter2020-04-066-25/+64
| |
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-11 11:05:31 +0000