| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
Allow bold for default colours
|
| | |
|
|/
|
|
| |
doesn't exist
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|
|
|
|
| |
Fix https://github.com/profanity-im/profanity/issues/1453
|
| |
|
|
|
|
|
|
| |
There is a small typo in src/config/theme.c.
Should read `certain` rather than `certian`.
|
|
|
|
|
|
| |
- Add NetBSD as a recognized platform without -ldl.
- Allow building with NetBSD libcurses instead of ncurses.
- Portability to NetBSD sh - use POSIX '=' instead of '=='.
|
| |
|
|
|
|
|
|
| |
This reverts commit 9b55f2dec0ea27a9ce4856e303425e12f866cea2.
Sorting the includes creates some problems.
|
|
|
|
| |
Regards https://github.com/profanity-im/profanity/issues/1396
|
|
|
|
|
| |
It just does a free.
Related to b580b9ef119045f142fa4baa9689a1c5ce8864ef
|
|
|
|
| |
Fix https://github.com/profanity-im/profanity/issues/1380
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
https://github.com/profanity-im/profanity/commit/98c38dc6d6d29333c63f80327774f094610d8602
sets C99 as standard.
strdup() is not part of C99.
For now set `-D_POSIX_C_SOURCE=200809L` macro to have strdup() in C99.
Using `gnu99` instead would be another option.
We should take more care to use glib functions whenever possible.
Regards https://github.com/profanity-im/profanity/issues/1357
|
| |
|
|
|
|
|
|
| |
`profanity -t bios` loads the bios theme now.
Fix https://github.com/profanity-im/profanity/issues/1286
|
|
|
|
|
|
| |
`/titlebar use name|jid` -> `/titlebar show|hide name|jid`
Fix https://github.com/profanity-im/profanity/issues/1284
|
|
|
|
| |
Use `main.trackbar` in themes.
|
|
|
|
| |
Fix https://github.com/profanity-im/profanity/issues/1264
|
|
|
|
| |
Copy paste error. We actually set the omemo char..
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
So far when loading a theme it also overwrote the preferences the user
set.
Lengthy discussion can be found at
https://github.com/profanity-im/profanity/issues/1077
Now we use `/theme load themename` to load the [colours] part of a
themem only.
`/theme full-load themename` will load the complete theme including
preferences set in there.
Regards https://github.com/profanity-im/profanity/issues/1077
|
|
|
|
|
|
| |
Make _theme_list_dir() static.
Sort _load_preferences() loadings accoding to type.
Add comments.
|
|
|
|
| |
Add `/titlebar use [name|jid]`.
|
|
|
|
|
|
|
| |
`/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.
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
Rename some things and use a swtich instead of if.
|
|
|
|
|
|
| |
Implement settings for redgreen and blue blindness.
Regards https://github.com/profanity-im/profanity/issues/1191
|
|
|
|
|
|
|
|
|
| |
* 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.
|
| |
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Might be related to https://github.com/profanity-im/profanity/issues/1186
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
| |
Seems this can cause trouble in case we cant use the theme properly.
|
| |
|
|
|
|
|
|
| |
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.
|