about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
...
* | | Add makefile target for spell checking and all testsMichael Vetter2021-10-051-0/+5
|/ /
* | Add codespell info to contributingMichael Vetter2021-10-011-0/+5
| |
* | Add codespell configMichael Vetter2021-10-011-0/+2
| |
* | Fix typos in apidocsMichael Vetter2021-10-014-6/+6
| |
* | Fix typo in profapi.hMichael Vetter2021-10-011-2/+2
| |
* | Fix fromat string in statusbarMichael Vetter2021-09-291-7/+7
| | | | | | | | Regards https://github.com/profanity-im/profanity/issues/1597#issuecomment-930540261
* | Fix wrong format string in titlebarMichael Vetter2021-09-291-3/+3
| | | | | | | | | | | | | | See https://github.com/profanity-im/profanity/commit/fd9ccec8dc604902bbb1d444dba4223ccee0a092 and https://github.com/profanity-im/profanity/issues/1597#issuecomment-930426764.
* | Merge pull request #1598 from profanity-im/feature/global-pluginsMichael Vetter2021-09-296-109/+84
|\ \ | | | | | | Improve plugins user experience
| * | Add more help about how to use pluginsMichael Vetter2021-09-292-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `/plugins install` installs a plugin to `.local/share/profanity/plugins`. And also loads it. When a plugin is loaded it will automatically be added to the `profrc` file like this: ``` [plugins] load=my.py; ``` On the next start Profanity will try to load this plugin again unless `/plugin unload my.py` is called.
| * | Fix `/plugins update ~/dir`Michael Vetter2021-09-291-7/+2
| | | | | | | | | | | | | | | | | | | | | | | | If `~/dir` exists profanity exits for me. Whole code for updating plugins from a dir isn't even implemented. Even though some messgages suggest otherwise. Remove this and only allow updating of one file.
| * | Remove Ruby commentMichael Vetter2021-09-291-2/+0
| | | | | | | | | | | | | | | | | | There most likely won't ever be Ruby plugins. Regards https://github.com/profanity-im/profanity/issues/779
| * | List globally available pluginsMichael Vetter2021-09-292-1/+37
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Packagers can package https://github.com/profanity-im/profanity-plugins or another collection of plugins to `/usr/local/share/profanity/plugins` (python) and `/usr/local/lib64/profanity` (c). `/plugins` will list these globally available plugins now along with the ones thare are installed (`~/.local/share/profanity/plugins`) and loaded. Regards https://github.com/profanity-im/profanity/issues/945
| * | Look for plugins to install in global locationMichael Vetter2021-09-292-12/+38
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Two options to install plugins. Mention the whole path: `/plugins install ~/src/profanity-plugins/my.py` Mention only the plugin name: `/plugins install my.py` The latter will look in `/usr/local/share/profanity/plugins/` for the file and copy it over to `~/.local/share/profanity/plugins`. At first I was thinking about loading the plugins from the global location. But users most likely don't want to have all plugins activated that an admin installs on a system. Regards https://github.com/profanity-im/profanity/issues/945
| * | Clean sourcepath from profrcMichael Vetter2021-09-291-0/+5
| | | | | | | | | | | | See 3b3a6b7a756e0f162d212249750524b7ce045cea for sourcepath removal.
| * | Remove `/python sourcepath`Michael Vetter2021-09-295-90/+5
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I feel like this mostly is confusing people. Also don't see much value for it. To me it looks like a regular workflow is like: ``` /plugin install ~/src/profanity-plugins/my.py ``` The whole thing with sourcepath, install (which also loads without having that described anywhere), load etc is confusing. Also each plugin file that is present in `.local/share/profanity/plugins` will then be auto loaded. Which means after installation.
* | Fix wrong format string in titlebar encryptionMichael Vetter2021-09-291-2/+2
| | | | | | | | | | | | Fix https://github.com/profanity-im/profanity/issues/1597 Thanks @debacle.
* | Start new cycleMichael Vetter2021-09-2899-5390/+2
| |
* | Release 0.11.1Michael Vetter2021-09-28101-3/+5408
| |
* | Fix typosMichael Vetter2021-09-222-7/+7
| |
* | Add more keybindings to /help navigationMichael Vetter2021-09-151-2/+5
| |
* | man: add more keybindingsMichael Vetter2021-09-151-0/+21
| |
* | cmd_funcs: Use glib functionMichael Vetter2021-09-091-2/+2
| |
* | notifier: Use glib functionMichael Vetter2021-09-091-3/+2
| |
* | Enable whole word only notifications by defaultMichael Vetter2021-09-081-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Set PREF_NOTIFY_MENTION_WHOLE_WORD to true. If I'm not mistaken the _mucwin_print_mention() / get_mentions() functions only work correctly since 6bc440c6f7e8c2c40d2d45f5c0decc15821abc8b. This changed the behaviour for users. They got notified when their nick was `kaffee` and in the message the string `kaffeekanne` occured. Setting `/notify room mention word_whole` corrected this. So my idea is that only now the mention function work correctly. And to have a good default behaviour we should set the `word_whole` on by default. Regards https://github.com/profanity-im/profanity/issues/1578
* | Mention keybindings in man pageMichael Vetter2021-08-311-0/+9
| |
* | Change attentionflag shortcut to alt+vMichael Vetter2021-08-312-2/+2
| | | | | | | | | | | | alt+f is the default readline shortcut for forward one word. Regards https://github.com/profanity-im/profanity/issues/1580
* | Merge pull request #1593 from a1346054/fixesMichael Vetter2021-08-2626-75/+61
|\ \ | | | | | | Minor cleanup
| * | Trim excess whitespacea13460542021-08-2620-64/+50
| | |
| * | Fix spellinga13460542021-08-261-3/+3
| | |
| * | License: use upstream license filea13460542021-08-261-4/+4
| | | | | | | | | | | | | | | File obtained from: https://www.gnu.org/licenses/gpl-3.0.txt
| * | Fix: files missing final ending newlinea13460542021-08-264-4/+4
|/ /
* | Merge pull request #1591 from paulfariello/fix/omemo-devicelist-access-modelMichael Vetter2021-08-203-22/+140
|\ \ | |/ |/| Fix OMEMO devicelist access model by reconfiguring it
| * Fix memleakPaul Fariello2021-08-201-0/+2
| |
| * Log error received while publishing OMEMO device listPaul Fariello2021-08-201-1/+2
| |
| * CosmeticPaul Fariello2021-08-201-1/+0
| |
| * OMEMO: Fix precondition-not-met handlingPaul Fariello2021-08-192-6/+15
| |
| * Create devicelist if it doesn't existsPaul Fariello2021-08-191-1/+18
| |
| * OMEMO: try device list creation and reconfigure on precondition-not-metPaul Fariello2021-08-193-8/+26
| |
| * Ensure devicelist access model is configured before updating itPaul Fariello2021-08-193-24/+96
|/
* omemo: always free error and print warningMichael Vetter2021-07-221-0/+9
| | | | Fix https://github.com/profanity-im/profanity/issues/1584
* Merge pull request #1587 from profanity-im/memleak-historyMichael Vetter2021-07-201-0/+4
|\ | | | | Fix memory leak in chatwin when load history (#1585)
| * chatwin: fix memory leak when load historyDmitry Podgorny2021-07-201-0/+4
|/ | | | | | | | _chatwin_history() reassigns msg->plain without freeing previous string. This leads to memory leak. As a temporary solution, free replaced string. Fixes #1585.
* Check for curl version nrMichael Vetter2021-07-201-1/+1
| | | | | | | We use `curl_url()` since e9d587578 which according to https://curl.se/libcurl/c/curl_url.html is only available in libcurl >= 7.62.0 . Related to https://github.com/profanity-im/profanity/issues/1581
* accounts: get rid of guard around freeMichael Vetter2021-07-171-11/+5
|
* Merge pull request #1583 from profanity-im/memleakMichael Vetter2021-07-172-12/+11
|\ | | | | Fix memory leak in accounts_get_login_status()
| * Reduce copy-paste in sv_ev_roster_received()Dmitry Podgorny2021-07-171-11/+5
| |
| * Fix memory leak in accounts_get_login_status()Dmitry Podgorny2021-07-172-1/+6
| |
* | Merge pull request #1586 from profanity-im/mentionsMichael Vetter2021-07-171-5/+6
|\ \ | |/ |/| Fix invalid reads on mentions in MUC
| * Don't handle /me in the middle of a message with mentionsDmitry Podgorny2021-07-171-2/+3
| |
| * Fix buffer overread in _mucwin_print_mention()Dmitry Podgorny2021-07-171-3/+3
|/ | | | | | Offset for g_utf8_substring() is higher than the string length. We can avoid g_utf8_substring() for the tail and simply convert starting offset to a pointer.
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-03 04:33:41 +0000