| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
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
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
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.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
Themes can now use color names from the xterm color name list [1].
1: https://jonasjacek.github.io/colors/
|
| |
| |
| |
| | |
Introduce `profanity -c` to specify an alternative config file.
|
| |
| |
| |
| |
| |
| |
| | |
Most applications have an 'apply changes' button. This makes testing
easier too.
Implement https://github.com/profanity-im/profanity/issues/1164
|
| | |
|
| | |
|
| |
| |
| |
| | |
Like discussed with James.
|
| |
| |
| |
| | |
Thanks to @kaffekanne for noticing this!
|
| |
| |
| |
| |
| |
| |
| | |
`/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
|
| |
| |
| |
| | |
There is a typo here. So this actually never worked ;-)
|
| |
| |
| |
| |
| |
| |
| | |
Wrapping for the occupants panel like already exists for the roster
panel. See `/occupants wrap on`.
Regards https://github.com/boothj5/profanity/issues/690
|
| |
| |
| |
| |
| |
| |
| |
| | |
`/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
|
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
With this feature user can configure TLS policy for an account and
override it for a single login with /connect command.
Example:
/account set <jid> tls force
/connect <jid> tls trust
The example shows how to trust server's certificate only once.
Fixes #1021.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
New tls policy "trust" added to /connect and /account. With the policy
TLS connection is established even with invalid certificate. Note, that
trust policy forces TLS connection and it fails when server doesn't
support TLS.
Examples:
/connect <jid> tls trust
/account <name> set tls trust
|
| |
| |
| |
| | |
Configuration windows are now being used by both muc and cmd.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|