-
-
Notifications
You must be signed in to change notification settings - Fork 237
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: sed invocations to work out of the box on macOS #615
Conversation
These fixes make the sed invocations run on macOS but I am not sure if they will break the GNU sed invocations in return…
From the GitHub Actions workflow:
This is what I was worried about, my changes made this portable for BSD |
The sed command line was difficult (impossible?) to be made portable so I just added macOS conditions.
Alright I just added macOS specific branches to the shell scripts and I call |
It seems that this will not work because I keep getting "sedi: command not found".
Yes, but I’m not sure why alias not working. Bash function is also good for
me.
Thank you for improving this!
|
This seems to work on my local so let's see if it runs in the CI on GitHub.
Not sure why VS Code went with 4.
…macOS as well Once harttle#615 is merged, the build script should work on macOS just as well as it does on Ubuntu and with this GitHub Actions matrix we can keep ensuring that it continues to work as it should.
…ld on macOS as well Once harttle#615 is merged, the build script should work on macOS just as well as it does on Ubuntu and with this GitHub Actions matrix we can keep ensuring that it continues to work as it should.
I am curious if Ubuntu will handle the newline…
…ld on macOS as well Once #615 is merged, the build script should work on macOS just as well as it does on Ubuntu and with this GitHub Actions matrix we can keep ensuring that it continues to work as it should.
# [10.8.0](v10.7.1...v10.8.0) (2023-06-03) ### Bug Fixes * proper error message for filter syntax error, [#610](#610) ([0480d33](0480d33)) * sed invocations to work out of the box on macOS ([#615](#615)) ([87d4cc7](87d4cc7)) ### Features * Add support for the Jekyll sample filter ([#612](#612)) ([ba8b842](ba8b842)) * introduce a matrix with latest Ubuntu and macOS to test the build on macOS as well ([82ba548](82ba548)), closes [#615](#615) * precise line/col for tokenization Error, [#613](#613) ([e347e60](e347e60))
🎉 This PR is included in version 10.8.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
* fix: sed invocations to work out of the box on macOS These fixes make the sed invocations run on macOS but I am not sure if they will break the GNU sed invocations in return… * fix: add macOS branches to the shell scripts The sed command line was difficult (impossible?) to be made portable so I just added macOS conditions. * Prototype the solution using an alias It seems that this will not work because I keep getting "sedi: command not found". * fix: use a Bash function instead of an alias to run sed portably This seems to work on my local so let's see if it runs in the CI on GitHub. * fix: use 2 spaces like the original scripts did Not sure why VS Code went with 4. * fix: use sedi for the build-changelog `1i\` part as well I am curious if Ubuntu will handle the newline…
These fixes make the sed invocations run on macOS but I am not sure if they will break the GNU sed invocations in return… I am hoping the GitHub Actions workflow will pass and config this is now portable between macOS and Ubuntu (what GitHub Actions is using).