about summary refs log tree commit diff stats
path: root/src/config
Commit message (Collapse)AuthorAgeFilesLines
...
* Add option to display MUC name or JID in titlebarMichael Vetter2020-01-233-0/+7
| | | | Add `/titlebar use [name|jid]`.
* Add `/roster room use` commandMichael Vetter2020-01-233-0/+7
| | | | | | | `/roster room use name` to use the name of the MUC in the roster list. `/roster room use jid` to use the jid of the MUC in the roster list. Display it only in case `/roster room by none` is set so far.
* XEP-0392: get background color from themeMichael Vetter2020-01-223-1/+17
| | | | | | | 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-034-4/+4
|
* Dont kill *.char preferences if theme doesnt contain itMichael Vetter2019-12-201-14/+0
| | | | | | | | | | | | | | | | | | | | | So far `/occupants char *`, `/roster contact char *`, `/roster room char #`, `/roster header char -`, `/occupants header char -` was saved and loaded from the preferences. But was overwritten when the theme was loaded. If the theme didn't set these values the value was just cleared. Despite that it might have been set in the users preferences. Funny enough the themes don't operate generally like this. For example `otr.char` is not cleared. This is again due to our borked theme/prefs concept (https://github.com/profanity-im/profanity/issues/1077). For now let's just use the one set from the preferences if it's set. The theme will however overwrite it if it is set there. Fix https://github.com/profanity-im/profanity/issues/1244
* Add /occupants color commandMichael Vetter2019-12-192-0/+4
| | | | | | | | `/occupants color on|off` to enable or disable XEP-0392 also for the MUC occupants. Regards https://github.com/profanity-im/profanity/issues/1191
* Add /roster color commandMichael Vetter2019-12-191-0/+3
| | | | | | | `/roster color on|off` to enable or disable XEP-0392 also for the roster. Regards https://github.com/profanity-im/profanity/issues/1191
* xep-0392: colorize rosterMichael Vetter2019-12-191-0/+1
|
* Improve color blindness handlingMichael Vetter2019-12-123-12/+16
| | | | Rename some things and use a swtich instead of if.
* Implement Color Vision Deficiencies settingMichael Vetter2019-12-123-7/+28
| | | | | | Implement settings for redgreen and blue blindness. Regards https://github.com/profanity-im/profanity/issues/1191
* XEP-0392: theme, ui: conditionally colorize user nicksAurelien Aptel2019-12-032-0/+7
| | | | | | | | | * add theme_hash_attrs() * when printing a user message check PREF_COLOR_NICK to decide whether to colorize it or not ideally we should hash the jid instead of the nick but this is already a first step.
* XEP-0392: color: implement color hashingAurelien Aptel2019-12-032-283/+376
| | | | | | | | | | * 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...)
* XEP-0392: config: add "color.nick" bool optionAurelien Aptel2019-12-032-0/+4
| | | | | the option will control whether to enable coloration of usernames based on the hashing algorithm described in XEP-0392.
* Add vim modelineMichael Vetter2019-11-1318-0/+18
|
* Change default text colors to default (#1213)Martin2019-10-221-8/+8
| | | | | | | | Change default themes text color Using "default" instead of white makes the default better readable when using a black/dark font on white/light background. May fix #535
* Rename identification fileMichael Vetter2019-10-161-1/+2
|
* Create random-bytes fileMichael Vetter2019-10-161-0/+1
| | | | | | | | | | So far only with dummy value. We will need an identifier that we can hash together with a message ID and put in as the origin-id. So when we receive message we can unsplit it and see if it was sent from this client. Regards https://github.com/profanity-im/profanity/issues/1207
* Null-set account structMichael Vetter2019-10-141-0/+1
| | | | Surpresses the valgrind warning about uninit. values.
* Add option to hilight unread rooms in /wins commandMichael Vetter2019-10-122-0/+3
| | | | | | | In the theme we can now set `cmd.wins.unread` to hvae a special color for the lines of the `/wins` output that have unread messages. Fix https://github.com/profanity-im/profanity/issues/895
* Fix preferences memory leakMichael Vetter2019-10-051-0/+4
| | | | | | Memory leak detected through unit tests. Regards https://github.com/profanity-im/profanity/issues/1019
* Merge pull request #874 from spiridoncha/masterMichael Vetter2019-10-052-0/+4
|\ | | | | Change /clear behaviour. Closes issue #855.
| * Makes /clear behavior configurable.Spiridonov Alexander2016-11-072-0/+4
| |
* | Introduce /reload commandMichael Vetter2019-10-042-18/+35
| | | | | | | | | | | | This command reloads the configuration file. Fix https://github.com/profanity-im/profanity/issues/627
* | Add coloring of statusbar.current tab in viewDaniel Lublin2019-09-242-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This theme color applies to the tab title text of the statusbar tab that is currently shown. The (somewhat confusingly named) `statusbar.active` theme color now applies to all other tabs (before, it applied to all tabs). Coloring of a tab that is highlighted/has new messages is done as before using the `statusbar.new` theme color. The default color is set to `cyan`, and thus causes no visible change for users -- until modified.
* | Set default color for main.text.historyMichael Vetter2019-09-111-0/+1
| | | | | | | | Might be related to https://github.com/profanity-im/profanity/issues/1186
* | Allow colorization of history messagesMichael Vetter2019-09-102-0/+2
| | | | | | | | | | | | | | | | History was always printed with `THEME_DEFAULT` we now use `THEME_TEXT_HISTORY` which is accesible in theme files via `main.text.history`. Fix https://github.com/profanity-im/profanity/issues/1170
* | 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.
* | Remove unused colour_string_t structMichael Vetter2019-08-231-5/+0
| |
* | theme: print to log not to consoleMichael Vetter2019-08-231-2/+1
| | | | | | | | Seems this can cause trouble in case we cant use the theme properly.
* | 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-232-1/+9
| |
* | color: Include log.hMichael Vetter2019-08-231-0/+1
| |
* | Reset color pairs when new theme is loadedMichael Vetter2019-08-231-0/+2
| | | | | | | | | | | | We only need the colour pairs initialized that the theme actually uses. It's otherwise possible that we run over the max value of initialzed pairs.
* | Reformat color.cMichael Vetter2019-08-231-5/+7
| |
* | Add header to color.hMichael Vetter2019-08-231-0/+34
| |
* | Use log_error() instead of g_warning()Michael Vetter2019-08-232-16/+19
| |
* | Add 256 colors supportAurelien Aptel2019-08-233-104/+437
| | | | | | | | | | | | Themes can now use color names from the xterm color name list [1]. 1: https://jonasjacek.github.io/colors/
* | Possibility to specify alternative config fileMichael Vetter2019-08-022-3/+8
| | | | | | | | Introduce `profanity -c` to specify an alternative config file.
* | Add 'save' command to save preferencesMichael Vetter2019-08-022-46/+8
| | | | | | | | | | | | | | Most applications have an 'apply changes' button. This makes testing easier too. Implement https://github.com/profanity-im/profanity/issues/1164
* | Set foreground color for untrusted messagesPaul Fariello2019-06-202-1/+3
| |
* | Use flags in xmmp/message.c for encryption and trustPaul Fariello2019-06-201-1/+2
| |
* | Add myself to copyrightMichael Vetter2019-06-172-0/+2
| | | | | | | | Like discussed with James.
* | Add omemo.char theme optionMichael Vetter2019-06-051-0/+8
| | | | | | | | Thanks to @kaffekanne for noticing this!
* | Add occupants charMichael Vetter2019-05-023-0/+47
| | | | | | | | | | | | | | `/occupants char` now sets a character that is displayed before the nick in MUCs. Similar like `/roster char` is displaying a char for the roster. Regards #690
* | Fix statusbar number in themeMichael Vetter2019-04-241-1/+1
| | | | | | | | There is a typo here. So this actually never worked ;-)
* | Add occupants wrap optionMichael Vetter2019-04-243-0/+5
| | | | | | | | | | | | | | Wrapping for the occupants panel like already exists for the roster panel. See `/occupants wrap on`. Regards https://github.com/boothj5/profanity/issues/690
* | Add occupants header charMichael Vetter2019-04-233-0/+47
| | | | | | | | | | | | | | | | `/occupants header char` now sets a character that is displayed before the role (moderator, visitor..) in a room. Similar to `/roster header char` is displaying a char for the roster. Regards https://github.com/boothj5/profanity/issues/690
* | Add /occupants indent commandMichael Vetter2019-04-183-0/+29
| | | | | | | | | | | | | | | | Roster has a `/roster contact indent` option. Now we have the same for occupants. So contacts in roster and in MUC can have configurable indentation. Regards https://github.com/boothj5/profanity/issues/690
* | Add OMEMO policyPaul Fariello2019-04-176-3/+93
| | | | | | | | | | | | | | | | | | | | | | | | There is 3 policy: - manual: OMEMO session are only started manually - automatic: OMEMO session are only started if they have been started manually before - always: OMEMO session are always started unless they have been ended manually before Closes #1040 and fixes #1052
* | Add random string at the end of the default resourcePaul Fariello2019-04-121-2/+4
| | | | | | | | | | | | | | | | When connecting for the first time or when creating a new account don't use only 'profanity' as default resource. Some server don't support having 2 connection with same resource. Using profanity as default lead to deconnections.
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2025-01-07 19:56:03 +0000