about summary refs log tree commit diff stats
path: root/src/config
Commit message (Collapse)AuthorAgeFilesLines
* let `account_new()` take ownership of passed valuesSteffen Jaeckel2023-01-183-110/+38
| | | | Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de>
* add `/strophe` command to modify libstrophe-specific settingsSteffen Jaeckel2023-01-182-5/+21
| | | | Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de>
* Update copyright yearMichael Vetter2023-01-107-7/+7
|
* 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.
* Apply codigng style on new MAM codeMichael Vetter2022-10-211-1/+1
|
* Add vCard supportMarouane L2022-10-183-0/+13
| | | | | | | | | | | | 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)
* Display a help message upon first start of ProfanityMichael Vetter2022-07-051-1/+0
| | | | Explaining how to register/connect/set up an account.
* accounts: deduplicate code via helper functionMichael Vetter2022-06-291-116/+54
|
* scripts: get rid of read variableMichael Vetter2022-06-291-4/+2
|
* Include xmpp.h to cafile.cMichael Vetter2022-06-281-0/+1
| | | | Was pulled in through log.h
* Display mood preferencesMichael Vetter2022-06-221-1/+1
|
* Make mood display optionalMichael Vetter2022-06-222-0/+5
|
* Don't forget encryption status for OX and PGP.MarcoPolo-PasTonMolo2022-06-174-14/+76
| | | | | | | | Use a pgp.enabled and ox.enabled array the same way that omemo.enabled is used. Fixes https://github.com/profanity-im/profanity/issues/1694 Fixes https://github.com/profanity-im/profanity/issues/733
* Update copyright yearMichael Vetter2022-05-096-6/+6
|
* Log encrypted messages by default to chatlogMichael Vetter2022-05-091-4/+4
| | | | | In case chatlogs are available lets log everything by default. Seems like most users expect this behaviour and I agree.
* ox: Add /ox log commandMichael Vetter2022-05-052-0/+7
|
* Restore default behaviour for stampsMichael Vetter2022-05-031-1/+1
| | | | | | | | | | | | @mdosch discovered that we now don't print `:` for messages from others anymore. Until https://github.com/profanity-im/profanity/pull/1663#issuecomment-1114625151 is fixed lets restore the default behaviour to always add `:` in `_win_print_internal()`. The result will be that a stamp set to `-->` will also look like `-->:`.
* Set default max log size to 10MBMichael Vetter2022-04-291-1/+1
| | | | In case logrotate is on.
* Merge branch 'master' into add_stamp_settingsMichael Vetter2022-04-284-15/+26
|\
| * Add support for offline MUC notificationsStefan Ott2022-04-232-0/+4
| |
| * Dont show presence status changes by defaultMichael Vetter2022-04-071-2/+2
| | | | | | | | | | | | | | | | | | | | | | Dont show presence status changes by default in chat and muc windows. Users repeatedly ask how to change this setting in the MUC. We have it in the FAQ since a long time. And most people I know change this setting, including me. So it looks like it's time to change this default.
| * Merge pull request #1674 from paulfertser/allow-bold-for-default-coloursMichael Vetter2022-04-041-12/+13
| |\ | | | | | | Allow bold for default colours
| | * Allow bold for default coloursPaul Fertser2022-04-011-12/+13
| | |
| * | Merge pull request #1681 from akaWolf/fix_theme_load_non_existMichael Vetter2022-04-031-0/+3
| |\ \ | | | | | | | | | | | | | | | | Fix theme load When we execute `/theme load somethingthatdoesntexist` it still loaded some colors wrongly.
| | * | disable execution of colors-changing code when call for theme load and it ↵Artjom Vejsel2022-04-021-0/+3
| | |/ | | | | | | | | | doesn't exist
| * / Include `config.h` in `src/config.cafile.c`Maxi Wuttke2022-04-021-0/+2
| |/ | | | | | | See <https://github.com/profanity-im/profanity/issues/1512>
| * run `make format`Steffen Jaeckel2022-03-301-1/+2
| | | | | | | | Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de>
* | Rename stamp preference variableMichael Vetter2022-04-282-8/+8
| | | | | | | | | | PREF_INCOMING_STR -> PREF_INCOMING_STAMP PREF_OUTGOING_STR -> PREF_OUTGOING_STAMP
* | add /stamp commandArtjom Vejsel2022-04-022-0/+12
|/ | | | command allow override standard stamps of incoming and outgoing messages
* Use EDITOR environment variablePaul Fertser2022-03-271-2/+4
| | | | | | | When preferences do not specify a program to be used for /editor command, try getting it from EDITOR (which POSIX.1-2017 calls one of "variables that are frequently exported by widely used command interpreters and applications"), fall back to "vim" if not set.
* add profanity-specific CAfileSteffen Jaeckel2022-03-223-0/+152
| | | | | | | | The profanity-internal mechanism to allow connecting to a server isn't easily portable to cURL. Therefor introduce a profanity-specific CAfile which is managed individually and will be configured in libcurl calls. Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de>
* a tad more `const`-correctnessSteffen Jaeckel2022-03-222-2/+2
| | | | Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de>
* also store PEM in `TLSCertificate`Steffen Jaeckel2022-03-222-4/+10
| | | | Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de>
* simplify codeSteffen Jaeckel2022-03-211-33/+1
| | | | Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de>
* replace `GString` usage where a simple `strdup` worksSteffen Jaeckel2022-03-141-20/+6
| | | | Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de>
* use `g_mkdir_with_parents()` instead of home-baked solutionSteffen Jaeckel2022-03-141-8/+7
| | | | Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de>
* add `files_file_in_account_data_path()`Steffen Jaeckel2022-03-132-0/+24
| | | | | | | | | | | | As all parts of the code invoking the `files_get_account_data_path()` function did the same afterwards, a function has been added with the same behavior. 1. create path 2. `mkdir` of that path 3. return final path Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de>
* auto-formatSteffen Jaeckel2021-10-271-1/+0
| | | | Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de>
* Allow utf8 in occupants header charMichael Vetter2021-10-223-20/+12
|
* Allow utf8 in occupants charMichael Vetter2021-10-223-19/+12
|
* Allow utf8 in roster room private charMichael Vetter2021-10-223-20/+12
|
* Allow utf8 in roster rooms charMichael Vetter2021-10-223-20/+12
|
* Allow utf8 in roster private charMichael Vetter2021-10-223-20/+12
|
* Allow utf8 in roster resource charMichael Vetter2021-10-223-20/+12
|
* Allow utf8 in roster contact charMichael Vetter2021-10-223-20/+12
|
* Allow utf8 in roster header charMichael Vetter2021-10-213-17/+15
| | | | | | | | | This and the following commits should make a couple of more configs allow utf8 chars so people can use their weird icons :-) We did the same for the otr/omemo/pgp indicators at: https://github.com/profanity-im/profanity/commit/1f8b1eb740391941e79e1004ad041f8178a2b674 https://github.com/profanity-im/profanity/commit/5cf6ee1bc6d0b99b01891bc455a657bf022a72b0
* Format code correctlyMichael Vetter2021-10-051-1/+1
|
* Clean sourcepath from profrcMichael Vetter2021-09-291-0/+5
| | | | See 3b3a6b7a756e0f162d212249750524b7ce045cea for sourcepath removal.
* Remove `/python sourcepath`Michael Vetter2021-09-292-5/+0
| | | | | | | | | | | | | | | | 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.
* 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
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-07-06 12:17:36 +0000