about summary refs log tree commit diff stats
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* 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.
* 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.
* 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.
* 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-103-2/+4
| | | | | | | | 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.
* 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.
* 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
* 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
|
* Add 256 colors supportAurelien Aptel2019-08-233-104/+437
| | | | | | 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.
* 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
|
* 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 #1167 from profanity-im/feature/specify-config-fileMichael Vetter2019-08-025-10/+18
|\ | | | | Possibility to specify alternative config file
| * Possibility to specify alternative config fileMichael Vetter2019-08-025-10/+18
| | | | | | | | Introduce `profanity -c` to specify an alternative config file.
* | Improve sv_ev_roster_received() last activity checkMichael Vetter2019-08-021-11/+9
|/ | | | | We don't need to do all the timing stuff if last activity is disabled anyways.
* Merge pull request #1166 from profanity-im/fix/1165-subscribed-msgMichael Vetter2019-08-021-2/+6
|\ | | | | Don't print subscribed message if contact is already in roster
| * Don't print subscribed message if contact is already in rosterMichael Vetter2019-08-011-2/+6
| | | | | | | | | | | | | | | | | | | | | | This occured with a user running Cisco Jabber. It seems this server sends repeated presence subscribed stanzas. And although I find this strange according to RFC this seems to be ok. So let's filter them and only display in the console output and to the log. But don't open seperate windows. Fix https://github.com/profanity-im/profanity/issues/1165
* | Add 'save' command to save preferencesMichael Vetter2019-08-026-46/+34
|/ | | | | | | Most applications have an 'apply changes' button. This makes testing easier too. Implement https://github.com/profanity-im/profanity/issues/1164
* Merge pull request #1163 from paulfariello/hotfix/command-execMichael Vetter2019-07-301-0/+7
|\ | | | | Fix memleak in /cmd exec
| * Fix memleak in /cmd execPaul Fariello2019-07-301-0/+7
| |
* | Merge pull request #1161 from profanity-im/fix/omemo-leakMichael Vetter2019-07-302-2/+4
|\ \ | |/ |/| Fix memleaks in OMEMO
| * Fix memleak in save_identity()Michael Vetter2019-07-231-1/+1
| | | | | | | | I don't see a reason for strdupping here.
| * Fix potential leak in omemo_untrust()Michael Vetter2019-07-231-0/+2
| |
| * Dont use not needed strdup() in save_identity()Michael Vetter2019-07-231-1/+1
| | | | | | | | I don't see a reason for strdupping here.
* | Fix command form submitPaul Fariello2019-07-301-1/+1
|/ | | | | Command form userdata were freed by iq_id_handler. We should now free the command ourself.
* Make sure result is always set for otr_get_policy()Michael Vetter2019-07-231-1/+1
|
* Merge pull request #1160 from profanity-im/fix/1159-groupaddsegfaultMichael Vetter2019-07-221-4/+0
|\ | | | | Fix segfault in group add/remove command
| * Fix segfault in group add/remove commandMichael Vetter2019-07-221-4/+0
| | | | | | | | | | Also regarding destructor. Fix https://github.com/profanity-im/profanity/issues/1159
* | Fix memleak in roster_change_name()Michael Vetter2019-07-221-2/+2
| |
* | Fix 3 leaks in cmd_funcsMichael Vetter2019-07-221-0/+4
| |
* | Fix several memleaks im cmd_ac.cMichael Vetter2019-07-221-0/+6
| | | | | | | | Exiting without freeing in some cases.
* | Fix memleak in roster_removeMichael Vetter2019-07-221-1/+1
| | | | | | | | strdup() is not needed here but will actually lead to a memleak.
* | Fix memory leak in roster_update()Michael Vetter2019-07-221-1/+2
| | | | | | | | current_name should not be const and should be freed.
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-07-10 11:51:45 +0000