about summary refs log tree commit diff stats
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* 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-065-59/+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
|
* db: dont log reflected MUC messagesMichael Vetter2020-04-061-1/+1
|
* db: log all incoming and outgoing messagesMichael Vetter2020-04-066-25/+64
|
* db: log outgoing message in one caseMichael Vetter2020-04-063-11/+46
| | | | Not all cases covered yet.
* db: add dedicated chat, muc, muc pm logging functionsMichael Vetter2020-04-063-9/+30
|
* Rename PROF_MSG_ENC_PLAIN to PROF_MSG_ENC_NONEMichael Vetter2020-04-066-23/+23
|
* db: insert message typeMichael Vetter2020-04-063-11/+22
|
* db: add more needed fieldsMichael Vetter2020-04-061-7/+20
| | | | DB fields should be complete now.
* db: make id autoincrementMichael Vetter2020-04-061-1/+1
|
* db: fix inserting null in databaseMichael Vetter2020-04-061-1/+1
|
* db: log replace idMichael Vetter2020-04-061-3/+3
|
* db: use goto in error caseMichael Vetter2020-04-061-24/+13
|
* db: add db versionMichael Vetter2020-04-061-1/+25
| | | | so we can later migrate.
* db: move includesMichael Vetter2020-04-063-7/+8
|
* db: guard against no DBMichael Vetter2020-04-061-2/+10
| | | | | | | | Maybe if we only use `/connect` we dont have ProfAccount. In that case we won't log anything. Only if a account is used we log. If this is the case or the init of the db didn't work we still want profanity to run but wont log anything to the db.
* db: Have one database per accountMichael Vetter2020-04-067-25/+47
|
* database: dont log muc pmsMichael Vetter2020-04-061-2/+0
|
* database: log stanza_id and whether it is a muc messageMichael Vetter2020-04-063-13/+13
|
* Add timestamp for incoming messages if none is setMichael Vetter2020-04-061-0/+6
| | | | | | | | Timestamps are only set if a message is delayed. If none is set let's set it upon recaival so we don't have to set it when it gets displayed. This means we will also have it for logs etc in the ProfMessage.
* database: log incoming messagesMichael Vetter2020-04-063-0/+40
| | | | First trial. Not covering all cases yet.
* database: Define chatlog database locationMichael Vetter2020-04-063-6/+29
|
* database: create tableMichael Vetter2020-04-061-2/+13
|
* Start SQLite db moduleMichael Vetter2020-04-063-0/+116
| | | | | | | | | | | | | | I plan to save all messages in an SQLite db. For retrieving information it's nicer than having it in a text file. We will have more info in there and easier to parse it. This will also be good for later MAM (https://github.com/profanity-im/profanity/issues/660). Regular text files will still be an option for users so that they can easily grep them and do whatever they like. Internally Profanity will only use the SQLite db.
* Fix multiple memory leaks related to rosterwin_roster()Dmitry Podgorny2020-04-061-0/+1
| | | | | There are multiple paths which lead to rosterwin_roster(). The function doesn't free list returned by wins_get_private_chats().
* Fix memory leak in cons_show_disco_info()Dmitry Podgorny2020-04-061-1/+1
|
* Fix memory leak in stanza_attach_correction()Dmitry Podgorny2020-04-051-0/+1
| | | | | | xmpp_stanza_add_child() takes own reference to the child stanza. Therefore we have to release our reference or the child is lost and not freed otherwise.
* Fix memory leak in _rosterwin_resources()Dmitry Podgorny2020-04-051-0/+1
|
* Dont have account otr setting if built without otrMichael Vetter2020-04-031-0/+2
|
* Merge pull request #1297 from profanity-im/memleak-mucwinMichael Vetter2020-04-031-0/+2
|\ | | | | Fixed memory leak in ProfMucWin
| * Fixed memory leak in ProfMucWinDmitry Podgorny2020-04-031-0/+2
| | | | | | | | | | Profanity remembers last message and its id for the message correction feature. We must free them in window destructor.
* | Dont have otr autocompletion if build without otr supportMichael Vetter2020-04-031-0/+16
| |
* | Dont have pgp autocompletion if build without pgp supportMichael Vetter2020-04-031-2/+16
| |
* | Dont even create OMEMO ac vars if we build without supportMichael Vetter2020-04-031-0/+10
| |
* | Only have OMEMO autocompletion if we build with OEMO supportMichael Vetter2020-04-021-2/+6
| |
* | Fix omemo autocompletion mitakeMichael Vetter2020-04-021-2/+0
|/ | | | | Don't return too early. We still need to check for regular omemo autocompletion (omemo_ac).
* Remove 'use' from titlebar autocompletionMichael Vetter2020-03-291-1/+0
| | | | This was forgotten in f13168005512fe4219741d9daf83681dd9ed3d63.
* Fix memory leak of presence objectDmitry Podgorny2020-02-231-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | The memory leak happens when a presence is received for a MUC room. The JID is not present in the roster, so updating its status is ignored. We have to free resource in this case, because it has no owner and is lost otherwise. ==25736== 47 (32 direct, 15 indirect) bytes in 1 blocks are definitely lost in loss record 1,625 of 3,399 ==25736== at 0x4A330FF: malloc (vg_replace_malloc.c:309) ==25736== by 0x13A962: resource_new (resource.c:47) ==25736== by 0x145501: _available_handler (presence.c:665) ==25736== by 0x145501: _presence_handler (presence.c:399) ==25736== by 0x145501: _presence_handler (presence.c:358) ==25736== by 0x80D5F34: handler_fire_stanza (in /usr/lib64/libstrophe.so.0.0.0) ==25736== by 0x80D2B49: _handle_stream_stanza (in /usr/lib64/libstrophe.so.0.0.0) ==25736== by 0x80E15CE: _end_element (in /usr/lib64/libstrophe.so.0.0.0) ==25736== by 0x843EE9B: doContent (in /usr/lib64/libexpat.so.1.6.10) ==25736== by 0x843F94B: contentProcessor (in /usr/lib64/libexpat.so.1.6.10) ==25736== by 0x8441E77: XML_ParseBuffer (in /usr/lib64/libexpat.so.1.6.10) ==25736== by 0x80D586B: xmpp_run_once (in /usr/lib64/libstrophe.so.0.0.0) ==25736== by 0x13E07E: connection_check_events (connection.c:119) ==25736== by 0x13869C: prof_run (profanity.c:129) Fixes #1279.
* Fix edit mistakeMichael Vetter2020-03-271-1/+1
|
* Upgrade examplesMichael Vetter2020-03-261-39/+39
|
* Add setting to not colorize own nick according to xep-0392Michael Vetter2020-03-257-5/+31
| | | | | | | | | | | | | | | | | | 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
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-08-19 08:58:20 +0000