Timeline for Are all bash scripts compatible with `zsh`?
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 26, 2019 at 2:10 | comment | added | Badr Elmers | thanks for signaling fish, if zsh is good then fish is super good for interactive usage at less | |
| Jun 5, 2019 at 7:28 | comment | added | Huygens | @KonradRudolph you know old habits die hard :shrug: but you're right. | |
| Jun 4, 2019 at 7:54 | comment | added | Konrad Rudolph | Hardg-coding the path to the shell is bad advice, even if it's done frequently. You should use #!/usr/bin/env bash instead, especially on macOS, where the default bash is severely outdated and new versions are virtually always installed into a different path. | |
| Mar 14, 2019 at 1:19 | history | edited | user232326 | CC BY-SA 4.0 | Typos |
| Jun 13, 2018 at 14:23 | comment | added | Huygens | @LCB I guess so. But I usually run my scripts without invoking source. I only source “scripts” which are more configuration file (e.g. export, alias, etc.). Those need some adaptations if they contain functions or bashism. Btw, I’m using now fish instead of zsh. | |
| Jun 13, 2018 at 10:58 | comment | added | LCB | But if the line #!/bin/bash will be ignored if running the script file like source ./script.sh? | |
| Jun 3, 2016 at 8:44 | comment | added | neaumusic | can you list your .zshrc :) | |
| May 8, 2012 at 20:39 | comment | added | Huygens | None. My personal scripts add the proper reference to bash and I had found a good .zshrc to start with. Zsh and bash were enough similar that I did not really find it challenging. | |
| May 8, 2012 at 20:37 | vote | accept | chrisl-921fb74d | ||
| May 8, 2012 at 20:36 | comment | added | chrisl-921fb74d | What was your most challenging part of switching over? | |
| May 8, 2012 at 20:35 | history | answered | Huygens | CC BY-SA 3.0 |