Thanks.
The character ;
will continue to have space removed before it if done after tab completion.
Thanks.
The character ;
will continue to have space removed before it if done after tab completion.
ok do you know how to do it similarly to kali?
ah ok, whats the reason?
ah ok got you.
I downloaded some Kali packages on Debian Unstable at that time and it looked good. See the last link, it is an Xfce colorscheme then you have to edit the terminal > preferences > colorscheme.
I was planning on doing the Xfce adaptation of Kali to Whonix, but got occupied.
Thanks!
Merged and uploaded to Whonix 17 testers repository.
The missing space before &&
seems fixed to me.
setup-dist
is no longer auto started with zsh. This is important for Whonix CLI.
For bash this is implemented in:
How could we do something similar for zsh?
Probably bad idea to make zsh parse /etc/profile
and /etc/profile.d
?
Is there an equivalent for /etc/profile.d
for zsh?
Thanks, merged!
Should the code for parsing /etc/zprofile.d
be moved to the very bottom of the script? Why:
/etc/zprofile.d
have an issue.Keeping in mind:
bash /etc/profile.d
:
login
, real terminal (tty
).zsh /etc/zprofile.d
:
login
, real terminal (tty
).For bash, therefore /etc/X11/Xsession.d
needed to be used because there’s no /etc/bashrc.d
.
To run in login shell only so this does not re-run for all terminal emulators tuning in X11 (GUI). Pseudo code:
if ! tty | grep -q /dev/tty ; then
true "$0: Not running in a login shell, not parsing /etc/zprofile.d folder."
return
exit 0
fi
Minor point: Why return and exit? return
only works for source
ed. Does not work when executed (for testing purposes).
Now that noexec made a ton of progress…
Can zsh help with the interpreter lock?
Do you think zsh restricted mode is useful for this?
Qubes dom0:
sudo xl console vmname
Looks messed up probably due to colors.
Perhaps based on
echo "$TERM"
vt220
don’t use colors?
feature request: support the no color environment variables
Similar to dist-installer-cli.
if test -n "${NO_COLOR:-}" || test -n "${ANSI_COLORS_DISABLED:-}"; then
No, rzsh
,rbash
or any r shell is too restricted, can’t even cd
.
Some are related to colors, but I tried removing it and it still looks very bad because of some zsh
specific escape sequences that I couldn’t figure out how to disable.
Use bash when using vt220
.
I’m unhappy with this decision. The shell will always be difficult to use for non-technical people, bash vs zsh makes no difference.
This feels more like a personal preference of the developers, rather than a technically sound decision. Like making $EDITOR
something other than nano.
Plain bash is standard in almost every single distribution, I don’t think Whonix should differ. I hope that the change can be undone in a future release.
I would also like to add that the disclaimer in bash should be removed, as it has been in zsh.
A question (and critique depending on answer), is that you can’t change default shell without modifying the template in Qubes-Whonix. This is very bothersome for multiple reasons (needing to clone, risking editing default templates, VM fingerprinting, having to restart, etc).