Skip to content
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

Bracket escaping in run scripts is lost when running synx #123

Open
krider2010 opened this issue Dec 15, 2016 · 1 comment
Open

Bracket escaping in run scripts is lost when running synx #123

krider2010 opened this issue Dec 15, 2016 · 1 comment

Comments

@krider2010
Copy link

Like many, we have a build script that flags up TODO: in code. However, I've discovered that every time I run synx that it loses the \ before the brackets which then breaks the compilation as the script fails.

Steps to reproduce:

  1. Add a run script as a build phase with contents like http://krakendev.io/blog/generating-warnings-in-xcode
  2. Run synx
  3. Try and compile (will fail on the script)
  4. Check the script and notice that the brackets are no longer escaped

Desired outcome:
3 succeeds and 4 is not necessary 😀

@iwheelbuy
Copy link

Same here I think...

used to be

TAGS="Error handle required"
find "${SRCROOT}" \( -name "*.h" -or -name "*.m" -or -name "*.swift" \) -print0 | xargs -0 egrep --with-filename --line-number --only-matching "($TAGS).*\$" | perl -p -e "s/($TAGS)/ warning: \$1/"

became

TAGS="Error handle required"
find "${SRCROOT}" ( -name "*.h" -or -name "*.m" -or -name "*.swift" ) -print0 | xargs -0 egrep --with-filename --line-number --only-matching "($TAGS).*$" | perl -p -e "s/($TAGS)/ warning: $1/"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants