about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* Move setup for AESGCM to omemo/cryptoWilliam Wennerström2020-11-164-64/+68
|
* Reformat HTTP get URL to AESGCM schemeWilliam Wennerström2020-11-163-31/+100
|
* Refactor to use file streamWilliam Wennerström2020-11-164-72/+57
|
* Initial /sendfile OMEMO encryptionWilliam Wennerström2020-11-168-54/+242
|
* Declare counter var inside loopMichael Vetter2020-11-0922-163/+94
| | | | We require c99/gnu99 anyways.
* Dont initialize i twice in accounts_get_account()Michael Vetter2020-11-051-5/+5
|
* Simplify _correction_autocomplete()Michael Vetter2020-11-051-4/+1
|
* Simplify _executable_autocomplete()Michael Vetter2020-11-051-4/+1
|
* Simplify _lastactivity_autocomplete()Michael Vetter2020-11-051-9/+4
|
* Simplify _who_autocomplete()Michael Vetter2020-11-051-3/+0
|
* Simplify _tray_autocomplete()Michael Vetter2020-11-051-5/+1
|
* Simplify _sub_autocomplete()Michael Vetter2020-11-051-5/+1
|
* Simplify cmd_ac_complete_filepath()Michael Vetter2020-11-051-8/+1
|
* Simplify cmd_ac_complete()Michael Vetter2020-11-051-9/+3
|
* Get rid of str_contains()Michael Vetter2020-11-023-15/+2
| | | | We can use strchr() here.
* Remove non existent functionsMichael Vetter2020-11-021-8/+0
|
* Print all error stanzasMichael Vetter2020-10-301-5/+5
| | | | | | | | | | | | | | | | | | Regards https://github.com/profanity-im/profanity/issues/1435 So far we didn't print the error if it contained `<error type="cancel">`. It appears that the code always thought this is a service-not-available (so one is either blocked or the account doesn't exist) and printed `Recipient not found`. But there can be other errors as well. Like in above mentioned issue `not-allowed`. Let's just print the text. In case of the cancel type we still remove the jid from the chat sessions. I'm not entirely sure whether this needs to be done in other cases too.
* Fixed Date format for MAM requestDebXWoody2020-10-281-2/+2
| | | | | | | | | Using g_date_time_new_now_utc instead of g_date_time_new_now_local Using g_date_time_format(timestamp, "%FT%TZ") instead of "%FT%T%:::z" Edit: DebXWoody created this patch because ejabberd returned an error with the old date format.
* functest: dont link against tclMichael Vetter2020-10-221-1/+1
| | | | | | Regards https://github.com/profanity-im/profanity/issues/1354 point 3. Since we dont use tcl and just libexpect I don't think we actually need to link against it.
* Merge pull request #1433 from profanity-im/bookmarkMichael Vetter2020-10-191-0/+1
|\ | | | | xmpp/bookmark: don't use uninitialised field
| * xmpp/bookmark: don't use uninitialised fieldDmitry Podgorny2020-10-191-0/+1
|/ | | | | | | | | | When a bookmark is created with '/bookmark add' command, ext_gajim_minimize remains uninitialised in new bookmark object and is read further in _send_bookmarks(). Initialise the field with 0. Fixes #1432.
* functest: Make char constMichael Vetter2020-10-152-9/+9
|
* Merge pull request #1430 from spth/masterMichael Vetter2020-10-146-6/+6
|\ | | | | Since the string from strerror should never be modified, use const.
| * Since the string from strerror should never be modified, use const.Philipp Klaus Krause2020-10-146-6/+6
|/
* Merge pull request #1428 from profanity-im/use-after-freeMichael Vetter2020-10-091-1/+1
|\ | | | | Fix use-after-free which is introduced in cons_alert()
| * Fix use-after-free which is introduced in cons_alert()Dmitry Podgorny2020-10-091-1/+1
|/ | | | | | Commit f12161f fixes memory leak, but introduces use-after-free issue. Allocate new memory for win_name with g_strdup() since it is freed with g_free() later.
* travis: disable debian, ubuntu, fedora for nowMichael Vetter2020-10-091-6/+6
| | | | | Until we have fixed their build issues. (Py2/Py3 etc)
* Merge pull request #1426 from profanity-im/cleanup/newlibsMichael Vetter2020-10-0910-64/+19
|\ | | | | Cleanup/newlibs
| * configure: check for python3-configMichael Vetter2020-10-091-1/+2
| |
| * travis: add libstrophe to twMichael Vetter2020-10-091-0/+1
| | | | | | | | | | | | | | So far only libstrophe is in 0.10.0 on TW. Lets just add both since configure will choose libmesode anyways if both are installed. And we plan to deprecate libmesode later anyways.
| * Enable _handle_ox_chat() payload/body decryptionMichael Vetter2020-10-091-3/+0
| | | | | | | | | | This part of the code was waiting for xmpp_stanza_new_from_string() from libstrophe 0.10.0.
| * Use g_date_time_format_iso8601()Michael Vetter2020-09-302-10/+4
| | | | | | | | | | | | | | | | | | This partly reverts d3a387a0ec6e5265f625de87318be2de610efb01. For proanity 0.9.x we still wanted to support older glib versions so that we can be packaged for various linux distros. Now with 0.10 we want to move on.
| * Replace stanza_get_child_by_name_and_ns with ↵Michael Vetter2020-09-306-32/+10
| | | | | | | | | | | | | | | | xmpp_stanza_get_child_by_name_and_ns Replace our own stanza_get_child_by_name_and_ns() with the upstreamed xmpp_stanza_get_child_by_name_and_ns() provided by the new libstrophe/libmesode 0.10.0.
| * Require libstrophe/libmesode 0.10.0Michael Vetter2020-09-302-18/+2
| |
* | Fix memleak in cons_alert()Michael Vetter2020-10-071-0/+2
|/ | | | Close https://github.com/profanity-im/profanity/issues/1427
* Merge pull request #1424 from niacat/netbsdMichael Vetter2020-09-0714-18/+60
|\ | | | | NetBSD support
| * Avoid passing NULL pointers to curses functions.nia2020-09-043-9/+23
| | | | | | | | | | | | | | | | This allows profanity to work without segfaulting from NULL pointer dereferences when used with NetBSD libcurses. Basic functionality was tested, there may be more NULL pointer issues hiding.
| * Basic support for building on NetBSD.nia2020-09-0413-9/+37
|/ | | | | | - Add NetBSD as a recognized platform without -ldl. - Allow building with NetBSD libcurses instead of ncurses. - Portability to NetBSD sh - use POSIX '=' instead of '=='.
* Merge pull request #1421 from misaflo/theme-gruvboxMichael Vetter2020-08-271-1/+1
|\ | | | | Update gruvbox theme (background color)
| * Update gruvbox theme (background color)Florent Lévigne2020-08-271-1/+1
|/
* Merge pull request #1415 from profanity-im/gtk23Michael Vetter2020-08-101-3/+5
|\ | | | | configure: support gtk3 too
| * configure: support gtk3 tooMichael Vetter2020-08-041-3/+5
| | | | | | | | | | Make Profanity compilable with gtk2 and gtk3. Prefer the latter.
* | Merge pull request #1416 from profanity-im/memleaks2Michael Vetter2020-08-101-21/+7
|\ \ | |/ |/| Fix memory leak in _handle_chat()
| * Fix memory leak in _handle_chat()Dmitry Podgorny2020-08-071-21/+7
|/ | | | | jid_create() for attribute "to" was called twice and the 1st object was lost.
* Merge pull request #1413 from profanity-im/feature/mam-addtodb-nodupMichael Vetter2020-07-244-10/+46
|\ | | | | MAM: Only add each message once to database
| * database: Only insert if there is no entry with same archive_idMichael Vetter2020-07-231-4/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | archive_is is <stanza-id> or <result id=""> and should identify one message stable and uniquely. See XEP-0359: Unique and Stable Stanza IDs. We need this for example for this situation: * we go online with Profanity * we fetch all messages since yesterday * we add them to the db * we go offline * we go online with Profanity * we fetch all messages since yesterday * we only want to add the new ones So far we don't ask MAM "give me all since last 'id'" but since a certain date. In case no archive_id will be set, it will be `(null)` and thus should be inserted anyways because it won't find a value with (null) in that row. Because when adding we use `message->stanzaid ? message->stanzaid : "",` so it will be empty in such a case. Regards MAM: https://github.com/profanity-im/profanity/issues/660 Regards Stable IDs: https://github.com/profanity-im/profanity/issues/1207
| * Parse stanza-idMichael Vetter2020-07-233-6/+40
|/ | | | | | | | | | | | Add stable stanza IDs to ProfMessage struct. We parse this for 1:1 messages (MUC needs to be done too). <stanza-id> for live messages <result id="x"> for MAM messages Regards MAM: https://github.com/profanity-im/profanity/issues/660 Regards Stable IDs: https://github.com/profanity-im/profanity/issues/1207
* Fix memleak in win_print_outgoing_with_receipt()Michael Vetter2020-07-231-0/+1
| | | | | | We should actually process the receipts also in LMC I think. Regards https://github.com/profanity-im/profanity/issues/805
* parser.c: Use glibMichael Vetter2020-07-231-4/+4
| | | | | | | | We use malloc() to allcoate memory for the arguments. But later on in cmd_funcs.c we use g_strfreev() to free it. Let's use g_malloc() to allocate instead. Second change is to use g_malloc() and g_free() for a gchar.
* Fix /correct quotation marks usageMichael Vetter2020-07-234-2/+29
| | | | | | | Add new `parse_args_as_one()` function to just use everything after the command as the argument. Fix https://github.com/profanity-im/profanity/issues/1404
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-29 02:49:38 +0000