about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* minor changesSteffen Jaeckel2023-01-188-76/+49
| | | | | | | | | | | * fix typo * less code duplication * less `GString` usage * more `auto_gchar` usage * document connecting to servers supporting SASL ANONYMOUS * ignore valgrind output Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de>
* add `/strophe` command to modify libstrophe-specific settingsSteffen Jaeckel2023-01-1812-23/+194
| | | | Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de>
* Merge pull request #1787 from profanity-im/fix/1695-screensaverMichael Vetter2023-01-121-2/+3
|\ | | | | Fix xscreensaver detection
| * Fix xscreensaver detectionPaul Fertser2023-01-111-2/+3
|/ | | | | | | | | In 28a9605a1 we migrated from AC_CHECK_LIB which defines HAVE_LIBXSS automatically. With pkg-config way you need it explicit. And also x11 is needed or else linking will fail missing XFree(). Patch provided by Paul Fertser and comitted by jubalh. Thanks Paul! Fix https://github.com/profanity-im/profanity/issues/1695
* Update copyright yearMichael Vetter2023-01-1055-57/+57
|
* Update mailing list linkMichael Vetter2023-01-104-5/+5
|
* Merge pull request #1784 from ↵Michael Vetter2023-01-021-1/+15
|\ | | | | | | | | MarcoPolo-PasTonMolo/fix/1783-url-save-ac-filenames Make `/url save` autocomplete filenames after a url
| * Make `/url save` autocomplete filenames after a urlMarcoPolo-PasTonMolo2022-12-271-1/+15
| | | | | | | | | | | | | | | | | | | | Previously after the url if you pressed tab, even if you typed out a filepath, profanity would erase that and cycle through url autocomplete results. This patch solves that and autocompletes filepaths after the url. Fixes https://github.com/profanity-im/profanity/issues/1783
* | Remove srht ciMichael Vetter2023-01-021-1/+1
|/ | | | wstrm who maintains this to check our build against openbsd vanished :(
* Merge pull request #1774 from profanity-im/fix/formatMichael Vetter2022-10-261-1/+1
|\ | | | | Work around different clang-format versions
| * Work around different clang-format versionsMichael Vetter2022-10-261-1/+1
|/ | | | | | | | | | | | | | | | | | | | | | Locally I have clang-format 15.0.2. Our CI runs ubuntu-20.04 so it has 10.0. Seems like a default value changed but I can't find it. When I still had clang-format 14.x everything was fine and checking: https://releases.llvm.org/15.0.0/tools/clang/docs/ReleaseNotes.html#clang-format I only see irrelevant things. Someone on the llvm IRC channel sais "there is no guarantee" and "maybe a regression or intended change". But seems like noone knows which setting could be the one we need. Since I don't have a better solution for now I will just edit this by hand to apply to the clang-format version we have on the CI. Will look into updating this one. But in any case it would be best if the configuration file could have this setting so formatting works the same for all contributors.
* Merge pull request #1773 from mdosch/mam-loading-string-improvementMichael Vetter2022-10-221-1/+1
|\ | | | | Improve MAM loading string.
| * Improve MAM loading string.Martin Dosch2022-10-221-1/+1
|/ | | | | Replaced three dots `...` by a proper ellipsis `…`. Removed plenking (space between `messages` and ellipsis.
* Merge pull request #1772 from MarcoPolo-PasTonMolo/fix/segfault-mamMichael Vetter2022-10-221-2/+13
|\ | | | | Fix segfault when loading from MAM
| * Fix segfault when loading from MAMMarcoPolo-PasTonMolo2022-10-221-2/+13
|/ | | | | | When loading messages from MAM profanity would segfault. Reason was that we were freeing the timestamp of messages when displaying them and we needed it for loading MAM.
* Add another format commit to ignoreMichael Vetter2022-10-211-0/+1
|
* Apply codigng style on new MAM codeMichael Vetter2022-10-215-9/+9
|
* Let users scroll up againMichael Vetter2022-10-211-4/+0
| | | | | | | | | | | | We removed this so that we don't get "[SCROLLED]" in the titlebar when there is actually not more text available. But now with MAM we can enable this again so that the user can scroll up and load more text out of the database. Maybe this also could use a check. This reverts commit c84b1b5e5d038684a6a475a251b738c3c5ffb9a5.
* Add MAM test stubsMichael Vetter2022-10-212-0/+6
|
* Fix merge mistake in databaseMichael Vetter2022-10-211-1/+1
| | | | | When doing 3bdc14dbcf1114fa1ea68cd6f455eecf90a9ac5e I forgot an `,` before encryption
* Fix GSList handling in new MAM codePaul Fertser2022-10-211-13/+8
| | | | | This patch was provided by @paulfertser and applied by @jubalh. Thanks a lot Paul!
* Fix merge mistakeMichael Vetter2022-10-211-1/+1
|
* Merge MAM improvements from #1724Michael Vetter2022-10-2113-63/+494
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I think this PR already solves and improves the MAM situation a lot. What's @MarcoPolo-PasTonMolo still wanted to do in this branch is: * MAM for mucs * Check if url and quotes autocompletion works fine * Check if the api still works fine * Resolve conflicts Conflicts are solved with this commit. MAM for mucs can be another feature PR. The rest we can check while being on master. And more people can help testing.
| * Don't notify on MAM messagesMarcoPolo-PasTonMolo2022-08-201-7/+10
| |
| * Handle late deliveryMarcoPolo-PasTonMolo2022-08-205-27/+109
| |
| * Apply corrections when getting messages from dbMarcoPolo-PasTonMolo2022-08-121-1/+1
| |
| * Handle MAM when chatwin gets created from incoming messageMarcoPolo-PasTonMolo2022-07-102-1/+10
| |
| * Fix duplicate sent messages in dbMarcoPolo-PasTonMolo2022-07-101-2/+3
| |
| * Have ability to scroll through history even without MAMMarcoPolo-PasTonMolo2022-07-104-10/+13
| |
| * Handle scrolling down when buffer fills upMarcoPolo-PasTonMolo2022-07-105-15/+37
| |
| * CleanupMarcoPolo-PasTonMolo2022-07-054-13/+5
| |
| * Add loading history message on initial MAM requestMarcoPolo-PasTonMolo2022-07-055-3/+20
| | | | | | | | | | | | This prevents scrolling to top and initiating another MAM request while still fetching the initial one. Also free timestamp object in database.c
| * Fix initial MAM not displayingMarcoPolo-PasTonMolo2022-07-058-56/+69
| | | | | | | | | | | | Did this by waiting for a batch of MAM messages to arrive before prepending them to the buffer. Also limited the number of messages to fetch to 10 so that the user gets more frequent updates.
| * Add 'Loading messages' message when scrolling upMarcoPolo-PasTonMolo2022-07-044-5/+24
| |
| * Fech data from mam when all history gets displayedMarcoPolo-PasTonMolo2022-07-033-1/+52
| | | | | | | | | | | | Fetch from mam without displaying when all mam messages get received display new messages from db. Unstable, initial mam doesn't get displayed unless we start scrolling.
| * Get messages from history when scrolling up.MarcoPolo-PasTonMolo2022-07-039-9/+106
| |
| * On new chatwin fetch mam according to guidelines.MarcoPolo-PasTonMolo2022-07-035-39/+161
| | | | | | | | | | Taken from here: https://github.com/modernxmpp/modernxmpp/commit/cd3e871e55c2cff45dffd05d6e50380b99845849
* | Merge pull request #1757 from techmetx11/feature/1158-vcardMichael Vetter2022-10-2025-7/+3688
|\ \ | | | | | | | | | | | | Add XEP-0054 vCard support Regards https://github.com/profanity-im/profanity/issues/1158
| * | Add vCard supportMarouane L2022-10-1825-7/+3688
|/ / | | | | | | | | | | | | | | | | | | | | | | Only nicknames, photos, birthdays, addresses, telephone numbers, emails, JIDs, titles, roles, notes, and URLs are supported Due to the synopsis array not having enough space, `/vcard photo open-self` and `/vcard photo save-self` are not documented properly in the synopsis section of the `/vcard` command, but they are documented in the arguments section Fixed memory leak in vcard autocomplete (thanks to debXwoody)
* | Merge pull request #1768 from profanity-im/winmsg-autocompMichael Vetter2022-10-171-6/+28
|\ \ | | | | | | Improve /msg and /win autocompletion
| * | Fix autocompletion for lastactivityStefan Kropp2022-10-171-5/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `/lastactivity` used autocompletion for /status instead. There was no get/set autocompletion thus user had to write `/lastactivity get` to get the proper results. Original fix by Stefan at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021028 Proper commit message and adapted patch by jubalh. Co-authored-by: jubalh@iodoru.org
| * | Improve /msg and /win autocompletionMichael Vetter2022-10-171-1/+15
|/ / | | | | | | Let /win and /msg both autocomplete roster nickname and actual barejid
* | release guide: Use proper orderMichael Vetter2022-10-121-4/+6
| | | | | | | | Otherwise version will not be correct in generated man pages.
* | Start new cycleMichael Vetter2022-10-12103-5580/+1
| |
* | Release 0.13.1Michael Vetter2022-10-12106-4/+5596
| |
* | release guide: remove libmesodeMichael Vetter2022-10-121-1/+1
| | | | | | | | Deprecated
* | Merge pull request #1760 from techmetx11/fix/1759-asyncMichael Vetter2022-10-126-35/+16
|\ \ | | | | | | Replace `call_external`'s implementation with an async one
| * | Spawn external programs asynchronouslyMarouane L2022-10-126-35/+16
| | | | | | | | | | | | | | | | | | | | | | | | Drawback is that we can't check the exitcode anymore. But we were unsure why/when we need this, see: https://github.com/profanity-im/profanity/pull/1760/files#r980868708 Fixes https://github.com/profanity-im/profanity/issues/1759
* | | Merge pull request #1767 from profanity-im/fix/firststartMichael Vetter2022-10-121-3/+3
|\ \ \ | | | | | | | | Fix first start detection
| * | | Fix first start detectionMichael Vetter2022-10-111-3/+3
|/ / / | | | | | | | | | | | | | | | Only display help message on first start. This is a fixup for: https://github.com/profanity-im/profanity/commit/27a5c9d287e856bd774988b4066667db54b65de7