What shell do you use daily?

tcsh - because I never got friends with bash (too weird, too bloated for my taste), and after many years I'm simply used to its behaviour, mostly history, and I'm too lazy to learn sh (yet.)
I'm not even sure if today I would recommend (t)csh anymore.
Since it's actually a pretty good shell, and default standard on FreeBSD, I would recommend sh.
Anyways for scripting in any case: sh.
But of course, everybody should pick the shell suits best the own individual needs.
 
Bash is what I'm used to. I believe tcsh has been changed to sh as default for root on FreeBSD. On RedHat
sh is a symlink to bash. We have a couple of old servers, not open to the world, where tsch is still the default, but I can't script in it. If I have to script something on one of those I'd just use sh. (Or ask Maturin for help) :)

The most I do on any of those though is just <command> > command-date and I have to remind myself to use `` instead of $()
 
scottro said:
but I can't script in it. If I have to script something on one of those I'd just use sh. (Or ask Maturin for help)
Click to expand...
Dude! I don't know how to script in [t]csh. I once tried many years ago. I thought, 'Well, it's C-like, and if it's my shell, then let's also learn scripting in it.' I don't know how long it took me to gave up, and perhaps there could be some others maybe tell you otherwise, but to me scripting in [t]csh was a massive pain in the a...! Maybe I missed a point, or two, but my recommendation was: Waste of time to even try it! Don't script in [t]csh!
I use it as CLI, but every of my many scripts starts with #!/bin/sh
 
I started off on AT&T Unix systems, so I used a lot of Bourne shell (sh) -- written by Stephen Bourne -- and Korn Shell (ksh) -- written by .. well... David Korn.
See! You could name software "after yourself" during the Old Republic. :cool:

I actually "really liked" (and still do) Korn shell (ksh93, there's even a ksh2020 now)

When I moved to Berkeley Unix systems (aka BSD 4.x, NET/2, etc) I switched over to C-Shell (csh) .. and much later on to variants of what became bash/ash/etc.

Today on FreeBSD I use default (sh) -- and (bash) on Linux systems.
 
dkh said:
bash. I want a base line I can use across most platforms without much fuss.
Click to expand...
Same but it's still not perfect. Regularly trying to solve an error happening at the "last line", having errors based on context but not syntaxis, loops forgetting exit variables, here-documents not accepting code structure indentation, like C preprocessor lines, getting warped when a script line count is changed during runtime...
 
shells/zsh for command line, /bin/sh for scripting and single user mode.

But my configured shell in /etc/master.passwd is /bin/csh, which is exact the same as /bin/tcsh (actually, hardlinked).
I have one line in my ~/.tcshrc.mine to exec shells/zsh when it's available and executable somewhere in PATH environment variable AND specific marker file exists.

Code: 
if ( -X zsh && -f ~/.Use_zsh ) exec zsh

This way, when shells/zsh somehow unavailable (i.e., lost by failed upgrade), I can still work on /bin/csh just as before I've switched to shells/zsh. Unfortunately, history file cannot be shared between shells/zsh and /bin/csh, though.
 
Whatever shell is set for the user I'm currently working as on whatever machine I'm currently working on. For FreeBSD that means sh and csh, for Debian it is mostly bash. And so on.
I'm not very tied into whatever shell I use; I configure it so it has the aliases I'm used to, and a reasonable amount of command history. That's it.
 
i've always used bash despite it being bloated (like anything GNU), it's actually the one with the least awkward syntax for scripting in my experience and because it's pretty much the default shell in most distros my scripts can work anywhere without needing anything extra installed

i have tried zsh before back when i wanted to make a Gentoo setup that replicated macOS but it turned out to be too weird to me and i already was used to bash anyway (i know zsh is compatible with it for scripting but still)
 
tingo said:
Whatever shell is set for the user I'm currently working as on whatever machine I'm currently working on. For FreeBSD that means sh and csh, for Debian it is mostly bash. And so on.
I'm not very tied into whatever shell I use; I configure it so it has the aliases I'm used to, and a reasonable amount of command history. That's it.
Click to expand...
that used to be me up until i started learning scripting by myself, the shell i used quite mattered because of it so i ended up growing attached to one
 
tcsh only (for root too). The C shell language is a language to learn as all the other, but what bothers me is that a "C something" must have functions, otherwise call it in another way.
 
bash, just because I have a load of bash scripts that I wrote over the years, many on slackware, and because its always there. Of course, the syntax is hideous in many areas, but I can't be bothered with installing a different incompatible shell like zsh on all the boxes I have to work on, let alone porting lots of scripts to something else, too much hassle.
 
Unlike most people on this thread, my scripts are probably horribly primitive, many working in sh as well. But blackbird9, I thought I'd heard that zsh is compatible with bash, that is it will work with most bash scripts. I thought that was part of its attraction, that it works with both bash-isms, and csh-isms. Of course, don't remember where I'd read this. But for what it's worth, testing with zsh at one point, when I was just trying it, did work with some basic sh and csh stuff. This was longgg ago, though might have changed for all I know.

I think some, perhaps a few, Linux distributions I played with also had fish, which I found rather annoying, predicting what I was going to type (often the wrong thing if I typoed) and, if I'm remembering right, colored text.
 
I use sh on FreeBSD; used Bash longest on Linux, but never really had a reason to try anything else :p (my scripts are simple and most games were a delete of ba for #!/bin/sh to FreeBSD)

I use CMD on Windows (not a fan of PowerShell syntax)
 
scottro said:
I thought I'd heard that zsh is compatible with bash, that is it will work with most bash scripts. I thought that was part of its attraction, that it works with both bash-isms, and csh-isms. Of course, don't remember where I'd read this.
Click to expand...
this is probably available even in zsh's website, there also are some shell options you may also enable for even more compatibility with bash

scottro said:
But for what it's worth, testing with zsh at one point, when I was just trying it, did work with some basic sh and csh stuff. This was longgg ago, though might have changed for all I know.
Click to expand...
i kinda doubt a shell would change this drastically, i'd think an interpreter being compatible with old code is like a priority so that shit doesn't break

scottro said:
I think some, perhaps a few, Linux distributions I played with also had fish, which I found rather annoying, predicting what I was going to type (often the wrong thing if I typoed) and, if I'm remembering right, colored text.
Click to expand...
it's supposed to be like that, which also makes it the slowest shell of them all, which i absolutely hate
the only time i used it was when i first tried Manjaro on my laptop way back in 2020 (?), i thought it looked nice but seeing how awfully slow it was i just switched to bash (?)

Espionage724 said:
I use CMD on Windows (not a fan of PowerShell syntax)
Click to expand...
yeah that one has to have the most HIDEOUS syntax of them all, i dunno what microsoft thought that making commands huge as fuck would be any good
 
You must log in or register to reply here.
Back
Top