about summary refs log tree commit diff stats
path: root/src/config/color.c
Commit message (Collapse)AuthorAgeFilesLines
* Format code with clang-format 16Michael Vetter2023-04-141-1/+1
|
* Update copyright yearMichael Vetter2023-01-101-1/+1
|
* 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
|
* Update copyright yearMichael Vetter2022-05-091-1/+1
|
* Update copyrightMichael Vetter2021-01-081-1/+1
|
* Declare counter var inside loopMichael Vetter2020-11-091-8/+4
| | | | We require c99/gnu99 anyways.
* Basic support for building on NetBSD.nia2020-09-041-0/+2
| | | | | | - Add NetBSD as a recognized platform without -ldl. - Allow building with NetBSD libcurses instead of ncurses. - Portability to NetBSD sh - use POSIX '=' instead of '=='.
* Apply coding styleMichael Vetter2020-07-071-291/+300
|
* Revert "Apply coding style"Michael Vetter2020-07-071-303/+294
| | | | | | This reverts commit 9b55f2dec0ea27a9ce4856e303425e12f866cea2. Sorting the includes creates some problems.
* Apply coding styleMichael Vetter2020-07-071-294/+303
| | | | Regards https://github.com/profanity-im/profanity/issues/1396
* XEP-0392: get background color from themeMichael Vetter2020-01-221-1/+8
| | | | | | | So far we just used -1 (default color). Now we actually check whether `bkgnd` is set in the theme file and use this if available. Fix https://github.com/profanity-im/profanity/issues/1255
* Update my Copyright to 2020Michael Vetter2020-01-031-1/+1
|
* Improve color blindness handlingMichael Vetter2019-12-121-8/+12
| | | | Rename some things and use a swtich instead of if.
* Implement Color Vision Deficiencies settingMichael Vetter2019-12-121-5/+10
| | | | | | Implement settings for redgreen and blue blindness. Regards https://github.com/profanity-im/profanity/issues/1191
* XEP-0392: color: implement color hashingAurelien Aptel2019-12-031-281/+364
| | | | | | | | | | * add the HSL values of each of the 256 terminal colors * add color_pair_cache_hash_str() * move common code to _color_pair_cache_get() helper func after hashing a string to a color, return the closest matching terminal color using euclidian distance of the HSL diff vector (this method was found empirically and seems to work well enough...)
* Add vim modelineMichael Vetter2019-11-131-0/+1
|
* Make sure memory in color_pair_cache_reset() was allocated.Michael Vetter2019-08-241-5/+8
| | | | | | | | Just to be on the safe side. Probably only relevant for unit tests where ncurses vars are not initialized with real values. Fix unit tests on all platforms.
* color: set capacity in unittest caseMichael Vetter2019-08-231-0/+5
| | | | Fix https://github.com/profanity-im/profanity/issues/1178
* Notify trying to load 256 colour theme in incapable terminalMichael Vetter2019-08-231-0/+7
|
* color: Include log.hMichael Vetter2019-08-231-0/+1
|
* Reformat color.cMichael Vetter2019-08-231-5/+7
|
* Use log_error() instead of g_warning()Michael Vetter2019-08-231-14/+17
|
* Add 256 colors supportAurelien Aptel2019-08-231-0/+418
Themes can now use color names from the xterm color name list [1]. 1: https://jonasjacek.github.io/colors/