about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* Set version to 0.7.1Michael Vetter2019-09-241-1/+1
|
* Merge pull request #1197 from mdosch/patch-5Michael Vetter2019-09-241-1/+1
|\ | | | | Fix typo
| * Fix typoMartin2019-09-241-1/+1
| | | | | | `Fix crash when jid has no not part` should probably mean `Fix crash when jid has no node part`.
* | Merge pull request #1195 from quite/statusbarcurrentMichael Vetter2019-09-244-4/+15
|\ \ | |/ |/| Add coloring of statusbar.current tab in view
| * Add coloring of statusbar.current tab in viewDaniel Lublin2019-09-244-4/+15
|/ | | | | | | | | | | | | | 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.
* Add 0.7.1 changelogMichael Vetter2019-09-241-0/+7
|
* Merge pull request #1192 from profanity-im/issue1186Michael Vetter2019-09-131-6/+16
|\ | | | | log: set nonblocking mode for stderr
| * log: set nonblocking mode for stderrDmitry Podgorny2019-09-131-6/+16
|/ | | | | | | 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.
* Merge pull request #1189 from mdosch/patch-4Michael Vetter2019-09-121-1/+1
|\ | | | | solarized: Set color for roster.header to default
| * Set color for roster.header to defaultMartin2019-09-121-1/+1
|/
* Log alleged roster push to fileMichael Vetter2019-09-121-0/+1
| | | | | | | | | | 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.
* Merge pull request #1187 from mdosch/patch-3Michael Vetter2019-09-121-0/+1
|\ | | | | Add color for main.text.history
| * Add color for main.text.historyMartin2019-09-111-0/+1
|/ | | Use the color schemes default for history.
* Print history color in theme propertiesMichael Vetter2019-09-111-0/+1
| | | | Also print `main.text.history` setting when `/theme properties' is run.
* 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-104-2/+5
| | | | | | | | 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
* Log 1:1 messages from other clients also to fileMichael Vetter2019-09-041-0/+4
| | | | | | Carbons where not logged so far. Fix https://github.com/profanity-im/profanity/issues/1181
* Set message->plain in carbon caseMichael Vetter2019-09-041-1/+8
| | | | | 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.
* Merge pull request #1183 from profanity-im/issue1153Michael Vetter2019-09-021-1/+3
|\ | | | | Don't crash if source jid doesn't contain the node part
| * Don't crash if source jid doesn't contain the node partDmitry Podgorny2019-08-261-1/+3
|/ | | | | | | | 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.
* Hardcode James email adress in info messageMichael Vetter2019-08-241-1/+1
| | | | Dont rely on PACKAGE_BUGREPORT being James' mail.
* 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.
* Merge pull request #1180 from mdosch/patch-2Michael Vetter2019-08-241-40/+41
|\ | | | | Update colors in solarized-dark theme
| * Update colors in solarized-dark themeMartin2019-08-241-40/+41
|/
* Merge pull request #1179 from mdosch/patch-1Michael Vetter2019-08-231-11/+11
|\ | | | | Change orange to orange1
| * Change orange to orange1Martin2019-08-231-11/+11
|/ | | | | `orange` is no allowed color[^1] so it is replaced by `orange1`. [^1]:https://jonasjacek.github.io/colors/
* 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
* Add color files to unittest sourcesMichael Vetter2019-08-231-0/+1
|
* Notify trying to load 256 colour theme in incapable terminalMichael Vetter2019-08-232-1/+9
|
* Add 256 colour info to /theme coloursMichael Vetter2019-08-231-0/+7
|
* 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
|
* Merge pull request #1177 from aaptel/colorsMichael Vetter2019-08-234-104/+438
|\ | | | | Add 256 colors support
| * Add 256 colors supportAurelien Aptel2019-08-234-104/+438
|/ | | | | | Themes can now use color names from the xterm color name list [1]. 1: https://jonasjacek.github.io/colors/
* omemo: use lower case to log infoMichael Vetter2019-08-231-1/+1
|
* Fix typo in OMEMO materials logMichael Vetter2019-08-231-1/+1
|
* Add comment about dead assignment in callback_add_timedMichael Vetter2019-08-231-0/+1
|
* Remove unused code in cmd_room() about win numMichael Vetter2019-08-231-6/+0
| | | | There is actually no reason to get the window number here.
* Move ISSUE_TEMPLATE into github folderMichael Vetter2019-08-231-0/+0
|
* Remove duplicate code in roster_updateMichael Vetter2019-08-231-9/+1
| | | | | Part of what `roster_update()` does manually is actually done in `roster_change_name()`.
* Use fixed email instead of PACKAGE_BUGREPORTMichael Vetter2019-08-231-1/+2
|
* Merge pull request #1174 from weiss/check-muc-delayMichael Vetter2019-08-213-2/+20
|\ | | | | Don't render (all) delayed messages as MUC history
| * Don't render (all) delayed messages as MUC historyHolger Weiß2019-08-203-2/+20
| | | | | | | | | | | | | | | | Double-check that a <delay/> tag on a groupchat message was actually added by the MUC service (rather than the sending client) before assuming it was received from the MUC history. Fixes #1173.
* | Merge pull request #1175 from mdosch/masterMichael Vetter2019-08-201-0/+78
|\ \ | |/ |/| Added solarized theme
| * Add solarized themeMartin Dosch2019-08-201-0/+78
|/
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-15 09:54:00 +0000