cm0002@programming.dev to Linux@programming.dev · 13 days agoWhat's involved in getting a "modern" terminal setup?jvns.caexternal-linkmessage-square21linkfedilinkarrow-up11arrow-down10cross-posted to: linux@lemmy.ml
arrow-up11arrow-down1external-linkWhat's involved in getting a "modern" terminal setup?jvns.cacm0002@programming.dev to Linux@programming.dev · 13 days agomessage-square21linkfedilinkcross-posted to: linux@lemmy.ml
minus-squaredarklamer@lemmy.dbzer0.comlinkfedilinkarrow-up0·13 days agoWhy would your login shell need to be fully POSIX compatible?
minus-squarefurikuri@programming.devlinkfedilinkarrow-up0·12 days agoThis was more of a problem when they didn’t support basic POSIX-isms so even basic calls to sh like sh -c 'echo "foo" && echo "bar"' would fail. Less of a problem now but you never know when a random script is going to rely on some obscure POSIX flag
minus-squaredarklamer@lemmy.dbzer0.comlinkfedilinkarrow-up0·12 days agoWhat does any of that have to do with your login shell?
minus-squarexav@programming.devlinkfedilinkarrow-up0·12 days agoScripts who use #!/bin/sh are independent of your login shell.
Why would your login shell need to be fully POSIX compatible?
This was more of a problem when they didn’t support basic POSIX-isms so even basic calls to
shlikesh -c 'echo "foo" && echo "bar"'would fail. Less of a problem now but you never know when a random script is going to rely on some obscure POSIX flagWhat does any of that have to do with your login shell?
Scripts who use
#!/bin/share independent of your login shell.