[FEAT] Sed differences across OSes #13

New Issue

Open

opened 2024-06-13 02:43:28 +00:00 by jakegoodwin · 1 comment

jakegoodwin commented

2024-06-13 02:43:28 +00:00

Owner

This is documented here --> https://unix.stackexchange.com/questions/663369/invalid-command-code-using-sed-to-replace-characters-inline

This should honestly be resolved for all the repos using the "otto.sh" script.

The sed program is different on FreeBSD+MacOS compared to linux distros for the most part. Most noticeable is that using the sed -i '' in freebsd causes and issue where it complains about invalid command code '.' This is documented here --> https://unix.stackexchange.com/questions/663369/invalid-command-code-using-sed-to-replace-characters-inline This should honestly be resolved for all the repos using the "otto.sh" script.

jakegoodwin added the

enhancement

label 2024-06-13 02:43:28 +00:00

jakegoodwin self-assigned this 2024-06-13 02:43:28 +00:00

jakegoodwin commented

2024-06-13 04:23:33 +00:00

Author

Owner

Also have found that the changing of the case lower-->upper for sed currently uses a GNUism, or a gnu style.

It should be changed out or have an option that doesn't have issues with this.

Also have found that the changing of the case lower-->upper for sed currently uses a GNUism, or a gnu style. It should be changed out or have an option that doesn't have issues with this.