@wolf480pl @cas it's easy...

The reasons one can despise something and the reason one appreciates it can be different.

I.e. I can appreciate #macOS for it's #accessibility right from the #installer but I can #despise it for #Apple not selling it as a commercial #Unix distro for a #subscription

Same with #bash: I can appreciate it for being better than #sh (unix-#shell) , #tcsh or #csh but I despise it for not having modernized like #fish.

• And with fish I appreciate it but I despise it's not the default #shell for any #Linux distro I can use in #production.

It's called having "mixed feelings" or rather #NuancedOpinion.

• Kinda like how every #skiddie and #TechIlliterate can use #Windows but that Windows is shit and the only reason they can is because they got groomed into being #consoomers that accept #enshittification as a fact of life.

@kenshirriff @b0rk Always default to enclosing file names and other argument strings to your #shell in 'single quotes' unless you want it mucked about with substituting $ENVIRONMENT_VARIABLES or multiple?filename*wildcard[s]

"Double quotes" will honor the spaces but also tell your shell to look for the non-alphabetic characters you can use to signal it to do something special.

@darrenmoffat #FreeBSD switched the default shell for the root user to #sh since FreeBSD 14.0. I use #zsh for my user account, but since it's installed using pkg, I don't want to risk locking myself out of my root account by using it as a shell there. #tcsh would be fine too, and is also part of FreeBSD base. I don't actually know the difference between #tcsh and #csh.

@jornane is the#csh actually #tcsh ? Have you tried #zsh ? I started with real Bourne #sh (AT&T) then real #csh (SunOS 4.x) briefly to #tcsh and then more than 30 years ago to #zsh. I only use #ksh (88 or 93) for scripting and #bash only on test systems because it is the default root shell on Solaris and many Linux systems.