Fix Bash syntax error in Mac set-login.sh script#1
Open
kylefmohr wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi! Thanks for sharing your dotfiles, lots of very useful stuff that I'm going to steal.
Gemini found a bug in this script and I was able to reproduce it.
snippet of Gemini's output
In bash, arrays are separated by spaces or newlines, not commas.
Because of the trailing commas on lines 5 through 9, the script is searching for a folder that literally ends in .app,. When it hits the [[ -d "$APP_PATH" ]] check, the Mac will say "that doesn't exist" and silently skip adding CleanShot, Expo Orbit, noTunes, Raycast, and Rectangle.
Reproduction
To verify Gemini's assertion, I modified the script to include the apps that start on login on my Mac:
then removed all items in System Settings > Login Items manually before running this script
This screenshot shows that the bug does in fact cause the behavior Gemini was talking about