| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Use `main.trackbar` in themes.
|
| |
|
|
|
|
| |
Dont duplicate code.
|
|
|
|
| |
Fix https://github.com/profanity-im/profanity/issues/1264
|
|
|
|
| |
Copy paste error. We actually set the omemo char..
|
|
|
|
|
|
|
|
|
| |
`/logging group color` has:
* `unanimous` which will color it with one unanimous color. Like it was
done always.
* `regular` which colors it like regular incoming messages.
Regards https://github.com/profanity-im/profanity/issues/1261
|
|
|
|
|
|
| |
`/pgp sendfile on` allows unencrypted file transfer in an PGP session.
Regards https://github.com/profanity-im/profanity/pull/1270
|
|
|
|
|
|
| |
`/otr sendfile on` allows unencrypted file transfer in an OMEMO session.
Regards https://github.com/profanity-im/profanity/pull/1270
|
|
|
|
|
|
|
| |
`/omemo sendfile on` allows unencrypted file transfer in an OMEMO
session.
Regards https://github.com/profanity-im/profanity/pull/1270
|
| |
|
|
|
|
| |
and print settings if only `/correction` is run.
|
| |
|
| |
|
|
|
|
| |
Fix a segfault if corresponding preference is not saved in config file.
|
|
|
|
| |
Fix #1068
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
Default is on. `revail.os=false` in the `connection` section of the
config can disable it.
A command to configure this will follow.
|
|
|
|
|
|
|
|
|
|
| |
Cannot be configured for now.
Can be set via `adv.notify.discoversion` in the `notification` section.
Will notify about version requests via XEP-0092 and XEP-0232.
Client version can still be seen via caps (capabilities).
See `stanza_attach_caps()`.
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
`/occupants color on|off` to enable or disable XEP-0392 also for the
MUC occupants.
Regards
https://github.com/profanity-im/profanity/issues/1191
|
|
|
|
|
|
|
| |
`/roster color on|off` to enable or disable XEP-0392 also for the
roster.
Regards https://github.com/profanity-im/profanity/issues/1191
|
| |
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
| |
* 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...)
|
|
|
|
|
| |
the option will control whether to enable coloration of usernames
based on the hashing algorithm described in XEP-0392.
|
| |
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
Surpresses the valgrind warning about uninit. values.
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
Memory leak detected through unit tests.
Regards https://github.com/profanity-im/profanity/issues/1019
|
|\
| |
| | |
Change /clear behaviour. Closes issue #855.
|
| | |
|
| |
| |
| |
| |
| |
| | |
This command reloads the configuration file.
Fix https://github.com/profanity-im/profanity/issues/627
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | |
|
| |
| |
| |
| | |
Seems this can cause trouble in case we cant use the theme properly.
|
| |
| |
| |
| | |
Fix https://github.com/profanity-im/profanity/issues/1178
|