about summary refs log tree commit diff stats
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* Move declaration and definition of win_get_last_sent_message to the correct ↵MarcoPolo-PasTonMolo2021-10-225-32/+33
| | | | place
* Remove autocomplete for /correct-editorMarcoPolo-PasTonMolo2021-10-214-31/+18
| | | | | | We decided that it was better to remove autocomplete for this command, since adding it only introduced problems and the command can still function perfectly without autocomplete.
* Export common code to helper functionsMarcoPolo-PasTonMolo2021-10-171-122/+72
|
* Add /correct-editor commandMarcoPolo-PasTonMolo2021-10-074-1/+153
|
* Format code correctlyMichael Vetter2021-10-0526-88/+84
|
* Fix history timestampMarcoPolo-PasTonMolo2021-10-051-6/+6
| | | | | | | Fixes https://github.com/profanity-im/profanity/issues/1423 Oldest stanza is fetched like before but now the timestamp is generated by creating date_time_from_iso8601 and then to_local, instead of trusting that the timestamp is in utc. The procedure previously was stamp = time_val_from_iso8601() then date_time = date_time_from_utc(stamp) then local_date_time = to_local(date_time)
* 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.
* 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.
* 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-291-2/+20
| | | | | | | | | | | | | | | | | | 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.
* Fix typosMichael Vetter2021-09-221-2/+2
|
* Add more keybindings to /help navigationMichael Vetter2021-09-151-2/+5
|
* 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
* 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
* 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
* 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.
* 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
| |
* | 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.
* Merge pull request #1576 from DebXWoody/autocomplete-untrustMichael Vetter2021-07-121-0/+27
|\ | | | | OMEMO autocomplete untrust
| * OMEMO autocomplete untrustDebXWoody2021-07-101-0/+27
| | | | | | | | Just a copy-past of autocomplete trust implementation.
* | Add limitations info to /help editorMichael Vetter2021-07-081-1/+3
| |
* | Add MAM notice to /help mamMichael Vetter2021-07-081-1/+3
| |
* | Fix segfault in /blocked with no argsMichael Vetter2021-07-061-1/+1
| | | | | | | | Fix https://github.com/profanity-im/profanity/issues/1575
* | Fix log rotationMichael Vetter2021-07-051-1/+1
| | | | | | | | | | | | Fix https://github.com/profanity-im/profanity/issues/1518 See https://github.com/profanity-im/profanity/issues/1518#issuecomment-870581988
* | cmd_blocked: Exit when wrong argumentsMichael Vetter2021-07-021-0/+1
| |
* | Initialize jidThorben Günther2021-07-011-2/+2
| |
* | XEP-0377: Fix arg parsingMichael Vetter2021-07-011-12/+23
| |
* | XEP-0377: Add forgotten namespaceMichael Vetter2021-07-012-0/+2
| |
* | Merge pull request #1566 from DebXWoody/bugfixing/oxMichael Vetter2021-07-016-52/+88
|\ \ | | | | | | Bugfixes for OX implementation
| * | OX bug fixDebXWoody2021-07-013-22/+22
| | | | | | | | | | | | | | | * Help / message description * C-Code format
| * | OX bug fixingDebXWoody2021-06-292-6/+12
| | | | | | | | | | | | | | | * Don't decryption if there is no private key * Decryption error messages
| * | Bugfixes for OX implementationDebXWoody2021-06-285-43/+73
| |/ | | | | | | | | | | | | * autocomplete for /ox discover * fixed help description * Implemented /ox char command * Validated KeyID length