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

carriage returns (\n's) in MAIN_TEXT and elsewhere #51

Open
wakco opened this issue Sep 20, 2021 · 0 comments
Open

carriage returns (\n's) in MAIN_TEXT and elsewhere #51

wakco opened this issue Sep 20, 2021 · 0 comments

Comments

@wakco
Copy link

wakco commented Sep 20, 2021

The depnotify.log must end up with the escaped carriage returns (\n's) in it, so the script needs to better escape the 's or it will put carriage returns into the file. I've ended up having to change the script to put them as \\n instead of \n.

I've been noticing my MAIN_TEXT only showing the first line in the dialog, and discovered the issue was because the \n's would go into depnotify.log translated to carriage returns, when depnotify.log requires the \n's.

I've been seeing this on macOS 10.15 and above, with DEPNotify 1.1.6 (I'm not using dev on macOS 10.14 or earlier, as we are treating 10.14 and earlier as unsupported).

@wakco wakco changed the title carriage returned (\n's) in MAIN_TEXT and elsewhere carriage returns (\n's) in MAIN_TEXT and elsewhere Sep 20, 2021
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

1 participant