about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* Fix `/plugins update`John Hernandez2023-04-191-31/+22
| | | | | | | | | | | Before it tried to unload the plugin first and check the output. But if broken plugin was loaded, then it couldn't unload it, so before it require uninstall and install after it, making update useless for plugin development purposes. Unload is part of the uninstall so no unload is needed inside of the cmd function. Refactoring of cmd_plugins_update.
* Merge pull request #1835 from H3rnand3zzz/fix/message-loggingMichael Vetter2023-04-182-19/+12
|\ | | | | Fix crash, add consistency to logging
| * Add logging consistencyJohn Hernandez2023-04-181-1/+2
| | | | | | | | | | | | | | Since MUC private messages are not logged by design, part where this logging happening is removed to add consistency. Add explanation in comment.
| * Fix `/log level` crashJohn Hernandez2023-04-181-18/+10
|/ | | | | | Fix crash caused by `/log level` command. Minor refactoring of command function.
* Merge pull request #1827 from H3rnand3zzz/feature/sessions-alarmMichael Vetter2023-04-1818-24/+180
|\ | | | | New Feature: Session Alarm
| * Add vscode support to .gitignoreJohn Hernandez2023-04-181-0/+1
| |
| * Add sessions_alarmJohn Hernandez2023-04-1817-24/+179
| | | | | | | | | | | | | | | | | | Introduce new feature: sessions_alarm. Added new account setting: max_connections. On exceeding this number, user will get an alert. If number is less than 1, no alert will happen. Tests altered to fit new feature.
* | Merge pull request #1829 from H3rnand3zzz/fix/readline-historyMichael Vetter2023-04-181-5/+8
|\ \ | | | | | | Don't add the same command twice to history
| * | Don't add the same command twice to historyJohn Hernandez2023-04-171-5/+8
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | Expected behaviour When you type /command /command it should be just 1 entry in the history. Behaviour All the entries were saved. Behaviour is changed by introducing check. Before adding to history, entry now is compared to the last history entry.
* | doscs: Add terminology section to man pageMichael Vetter2023-04-171-1/+13
| | | | | | | | | | | | | | Let's just define some basic terminology. In many sections of the /help we actually use these terms. This should help new users understand what they mean.
* | Merge pull request #1831 from profanity-im/man_encMichael Vetter2023-04-171-0/+21
|\ \ | | | | | | Add encryption section to man page
| * | Add encryption section to man pageMichael Vetter2023-04-171-0/+21
|/ / | | | | | | | | | | | | | | The goal should be that users can make a more informed decision about which encryption they actually want to use. We can also use this to document usage details of implementation quirks, if any.
* | Merge pull request #1830 from profanity-im/feat/codspellciMichael Vetter2023-04-151-0/+14
|\ \ | | | | | | Add spellcheck to CI
| * | Add spellcheck to CIMichael Vetter2023-04-151-0/+14
| | |
* | | docs: Add info about different clang-format versionsMichael Vetter2023-04-151-0/+2
|/ / | | | | | | | | Make this clear to new users. Since sjaeckel had reservations on https://github.com/profanity-im/profanity/pull/1828.
* | Merge pull request #1828 from profanity-im/newclangMichael Vetter2023-04-146-151/+144
|\ \ | |/ |/| Use GH action for code style check
| * Add another formatting commit to git blame ignoreMichael Vetter2023-04-141-0/+1
| |
| * Format code with clang-format 16Michael Vetter2023-04-144-134/+137
| |
| * Switch to clang-format check actionMichael Vetter2023-04-141-17/+6
|/ | | | | | | | | | | | Instead of running clang-format outselves on the old Ubuntu version. This let's us easily configure which version of clang-format we want to execute. Used action: https://github.com/marketplace/actions/clang-format-check Properly fix: https://github.com/profanity-im/profanity/pull/1774
* docs: Fix formatting in SECURITY.mdMichael Vetter2023-04-141-1/+2
|
* Merge pull request #1823 from H3rnand3zzz/fix/msg-crashMichael Vetter2023-04-142-7/+8
|\ | | | | Fix memory corruption crash
| * Cleanup p_ox_gpg_decryptJohn Hernandez2023-04-131-4/+6
| | | | | | | | | | | | In OX implementation gpgme's buffer remains untouched, thus not leading to the crash. But code can be shorter and more concise.
| * Fix memory corruption crashJohn Hernandez2023-04-131-3/+2
| | | | | | | | | | | | | | Under certain circumstances setting plain_str[len] to 0 might lead to crash and it does not follow the best practices as well. This change allows better handling of buffer copying and prevents crash.
* | Merge pull request #1826 from H3rnand3zzz/feature/roster-nickname-removeMichael Vetter2023-04-149-7/+65
|\ \ | |/ |/| Add nickname support for `/roster remove`
| * Add nickname support for /roster removeJohn Hernandez2023-04-139-7/+65
|/ | | | | | Add support of name/nickname instead of only JID for `/roster remove` command. Add tests for it as well.
* docs: add SECURITY.mdMichael Vetter2023-04-131-0/+6
|
* iq: initialize os and os_txtMichael Vetter2023-04-111-2/+2
| | | | | | | | | | | | Let's set this to NULL. Someone was using `picaur` and got an error about potential uninitialization. Even though the code is fine let's set this to NULL to make the compiler happy. The strange thing was that building manually on the same system worked. Related to 2e43b0ae62478bede34f6f52f73d22d671425f85.
* Merge pull request #1822 from H3rnand3zzz/fix/iq-osMichael Vetter2023-04-111-3/+2
|\ | | | | Hotfix stanza release
| * Fix releases of os and os_txt stanzasJohn Hernandez2023-04-101-3/+2
| | | | | | | | | | | | | | | | | | | | If custom client is not set and include_os is true, stanzas might be released without initializiting. This commit fixes it by introducing an additional check on usage of custom client. Related to commit e52ca2fbaa02acec3b2b757369ef5740e7a103da
* | Add test/valgrind section to PR templateMichael Vetter2023-04-101-0/+6
| |
* | Add limitation info about /statusbar chat user|jidMichael Vetter2023-04-101-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | While testing https://github.com/profanity-im/profanity/pull/1817 we found that: ``` /statusbar show name (I have this off by default /msg someone where I chose someone in my roster that has a nick assigned /statusbar chat jid ``` Will only take effect upon creation or redraw of that tab. Reason is that we do this in create_tab to limit building this dynamically. Let's leave it like it is but add a note to users. Not worth build that string all the time.
* | Merge pull request #1817 from H3rnand3zzz/feature/full-jidMichael Vetter2023-04-103-25/+57
|\ \ | |/ |/| JID Display in Titlebar and Fix
| * Fixes Statusbar tabs and CleanupJohn Hernandez2023-04-102-15/+39
| | | | | | | | | | | | | | | | | | | | - Fixes statusbar tabs. Bug: Statusbar used nickname if it was set in roster, irrelevant to /statusbar chat setting. Expected behaviour would be using this setting set as "user" to show nickname, and to show jid with "jid" setting. Other solution is to give a user control over it with another settings. - _status_bar_draw_maintext cleaned up, no changes to behaviour
| * Improve titlebar flexibilityJohn Hernandez2023-04-102-11/+19
|/ | | | | | | Before this change, only nickname or JID (if no nickname set) is shown in the titlebar. Change allows to alter nickname/JID preference using already implemented /titlebar show jid|name setting. If both are set to "show", then it is displayed in "nickname <JID>" format.
* contributing: add note about testingMichael Vetter2023-04-091-0/+1
|
* Rewrite description for clientidMichael Vetter2023-04-091-1/+1
|
* Merge pull request #1815 from H3rnand3zzz/feature/the-client-switcherMichael Vetter2023-04-0916-86/+151
|\ | | | | Feature: Allow setting client identification name/version manually
| * Allow setting client identification name/version manuallyJohn Hernandez2023-04-0916-86/+151
| | | | | | | | | | | | | | | | Add changes allowing user to switch client name and version. Useful for enhancing user privacy. Minor cleanup.
* | Merge pull request #1821 from mdosch/use-proper-ellipsis-charMichael Vetter2023-04-0910-28/+28
|\ \ | | | | | | User proper ellipsis char
| * | User proper ellipsis charMartin Dosch2023-04-0910-28/+28
|/ / | | | | | | | | | | | | As stated in https://github.com/profanity-im/profanity/pull/1820#issuecomment-1498083383 profanity uses "..." (three dots) in a lot of places instead the proper ellipsis char "…".
* | Merge pull request #1813 from profanity-im/tabmode-irssiMichael Vetter2023-04-087-46/+135
|\ \ | | | | | | add `/statusbar tabmode actlist`
| * | add `/statusbar tabmode actlist`Steffen Jaeckel2023-04-087-46/+135
|/ / | | | | | | | | | | | | | | | | | | The existing way how active tabs are displayed didn't allow showing more than 10 tabs. This patch adds a mode where the statusbar shows a comma-separated list of tabs which were active since the last time viewed. This view is inspired by how `irssi` shows the active tabs, therefore it is also called `actlist`. Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de>
* | Merge pull request #1814 from profanity-im/improvementsMichael Vetter2023-04-043-113/+118
|\ \ | | | | | | Improvements and bugfixes
| * | fix display of a "list type" in a form if there's no value assigned yetSteffen Jaeckel2023-04-041-27/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It is possible, that a server sends a form with a field as follows, which has no (default) value assigned. ``` <field label="foo" type="list-single" var="bar"> <option label="a"><value>a</value></option> <option label="b"><value>b</value></option> <option label="c"><value>c</value></option> </field> ``` This patch fixes profanity to show that list. Before this patch profanity showed nothing. I stumbled over this while running the `/room config` command inside a newly created muc on the `sure.im` XMPP server. Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de>
| * | refactor into array of a `struct`Steffen Jaeckel2023-04-041-5/+15
| | | | | | | | | | | | | | | | | | ...instead of having two separate arrays. Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de>
| * | only create hashtable onceSteffen Jaeckel2023-04-041-72/+74
| | | | | | | | | | | | | | | | | | | | | Before this change the same hashtable was re-created each time one used the auto-completion feature. Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de>
| * | fix memory leakSteffen Jaeckel2023-04-041-9/+8
|/ / | | | | | | | | | | | | | | `found` was leaked before This was somehow missed in e9aaba938b4f1b62b5f9018583a82ed7e7180977 Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de>
* | Merge pull request #1811 from shahab-vahedi/batman-fixMichael Vetter2023-04-031-2/+2
|\ \ | |/ |/| Fix color name in batman theme
| * themes/batman: Use "bold_black" iso "black_bold"Shahab Vahedi2023-04-031-2/+2
| | | | | | | | | | | | | | | | | | | | This makes all the related errors in the log files go away: ... prof: ERR: Color: bad color name black_bold_default prof: ERR: Unable to load colour theme ... Fixes https://github.com/profanity-im/profanity/issues/1810
* | Fix typosMichael Vetter2023-04-034-4/+4
| |
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-29 13:39:30 +0000