| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|/ / /
| | |
| | |
| | | |
Fixes compilation when using custom Python installed with pyenv.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Regards https://github.com/profanity-im/profanity/issues/618
|
| | |
| | |
| | |
| | |
| | |
| | | |
alt-a brings one to the next window with unread messages.
Regards https://github.com/profanity-im/profanity/issues/1114
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
alt-2 brings one ot the window.
irssi supports alt + 1234567890qwertyuio to easily switch to 20 windows
instead of just ten.
Hardcode this too.
Regards https://github.com/profanity-im/profanity/issues/1114
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Some versions of prosody send the domainpart.
See https://issues.prosody.im/1416
Workaround to handle those cases.
Thanks to Holger Weiss for helping with this!
Fix https://github.com/profanity-im/profanity/issues/1190
|
| | |
| | |
| | |
| | | |
Was left over from refactoring a long time ago.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If we pass a jid/nick to `/info` in a chat window we will still get the
output. But on the console window.
Regards https://github.com/profanity-im/profanity/issues/1194
|
| | |
| | |
| | |
| | | |
Regards https://github.com/profanity-im/profanity/issues/1194
|
|\ \ \
| | | |
| | | | |
Fix solarized dark theme
|
|/ / /
| | |
| | |
| | |
| | | |
This fixes a whitespace issue that was probably introduced
by using the github editor.
|
|\ \ \
| | | |
| | | | |
Update theme solarized dark
|
|/ / /
| | |
| | |
| | | |
The theme `solarized dark` is updated to play well with
the newly added `statusbar.active` from #1195
|
| | | |
|
|\ \ \
| | | |
| | | | |
Fix typo
|
| | | |
| | | |
| | | | |
`Fix crash when jid has no not part` should probably mean `Fix crash when jid has no node part`.
|
|\ \ \ \
| |/ / /
|/| | | |
Add coloring of statusbar.current tab in view
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | | |
|
|\ \ \
| | | |
| | | | |
log: set nonblocking mode for stderr
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | | |
Glib can print error messages to stderr and blocking write freezes
Profanity if the buffer is full. Move stderr to nonblocking mode
in hope that glib will skip printing on EWOULDBLOCK error. In this
case we lose some error messages, but Profanity continues working.
|
|\ \ \
| | | |
| | | | |
solarized: Set color for roster.header to default
|
|/ / / |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
https://gultsch.de/dino_multiple.html mentions CVE-2019-16235, CVE-2019-16236 and CVE-2019-16237.
CVE-2019-16235: Is checking the from in carbon messages. We do that.
CVE-2019-16236: Is checking the from in roster pushes. We do that but
didn't log it yet.
CVE-2019-16237: Is checking the form in MAM messages. We don't support
them yet.
|
|\ \ \
| | | |
| | | | |
Add color for main.text.history
|
|/ / /
| | |
| | | |
Use the color schemes default for history.
|
| | |
| | |
| | |
| | | |
Also print `main.text.history` setting when `/theme properties' is run.
|
| | |
| | |
| | |
| | | |
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
|
| | |
| | |
| | |
| | |
| | |
| | | |
Carbons where not logged so far.
Fix https://github.com/profanity-im/profanity/issues/1181
|
| | |
| | |
| | |
| | |
| | | |
message->plain should always contain something. In the case of the
carbons we forgot to set if rom the body in case it's empy.
|
|\ \ \
| | | |
| | | | |
Don't crash if source jid doesn't contain the node part
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Profanity uses the node part of a JID as display name for a tab. If such
a JID doesn't contain the node part, Profanity crashes on NULL pointer
dereference.
In the above case, use barejid which is just a domain. Fixes #1153.
|
| | |
| | |
| | |
| | | |
Dont rely on PACKAGE_BUGREPORT being James' mail.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
|\ \ \
| | | |
| | | | |
Update colors in solarized-dark theme
|
|/ / / |
|
|\ \ \
| | | |
| | | | |
Change orange to orange1
|
|/ / /
| | |
| | |
| | |
| | | |
`orange` is no allowed color[^1] so it is replaced by `orange1`.
[^1]:https://jonasjacek.github.io/colors/
|
| | | |
|
| | |
| | |
| | |
| | | |
Seems this can cause trouble in case we cant use the theme properly.
|
| | |
| | |
| | |
| | | |
Fix https://github.com/profanity-im/profanity/issues/1178
|
| | | |
|
| | | |
|
| | | |
|