https://github.com/Whonix/msgcollector
Makes sure that notifications by background services are seen by both GUI and Terminal users.
https://github.com/Whonix/msgcollector
Makes sure that notifications by background services are seen by both GUI and Terminal users.
This was done. If not, please create specific tickets where it isn't done.
Looks good on your side. Possibly a Qubes bug. I'll look into it in the next developers build.
Something strange. I can see it in my VM
Good quality, could merge into git master and ready for Whonix 14 already.
should fix the issues
In T456#11896, @joysn1980 wrote:The issue here is that - msgdispatcher_dispatch_x is a generic script, which displays the message that comes to it.
Now, the question is - what is the best way to find out a generic way to split a message into the below three parts
- Part that comes inside message being displayed
- Part that comes inside 'Show Details"
- Part that comes inside 'More Help'
The issue here is that - msgdispatcher_dispatch_x is a generic script, which displays the message that comes to it.
Now, the question is - what is the best way to find out a generic way to split a message into the below three parts
This is mostly a usability question. Wondering if better to only have a Show Details button or to have both, a Show Details and More Help button. How can we make such error messages most helpful for the user?
Another old task
Excellent! All merged.
whonix-setup-wizard, 1 change required, to be merged
So we are done with
From guimessages - 1 change required and it done
https://github.com/joysn/python-guimessages
From sdwdate-gui
br_add - nothing to add
striphtml nothing to add
generic_gui_message - done
tb_updater_gui - done
A few more projects are involved, where this is TODO. Btw there are all our components where python is involved.
Done in all involved components.
qvm-run --pass-io uses simple pipe (not virtual terminal), so it is
expected to not have TERM set.
Related, has it been considered for qvm-run --pass-io to set or not set environment variable TERM? I wonder if the current implementation is correct. @marmarek
We can close it.
Created a follow up task: T216
Thanks! Merged. And added a minor fix on top (right order for license header and shebang).
https://github.com/Whonix/msgcollector/commit/ef03b5dc44873e441207667df9b813a991c9fdd9