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

make help text not escaping newlines #303

Closed
benjamin051000 opened this issue Nov 8, 2024 · 1 comment
Closed

make help text not escaping newlines #303

benjamin051000 opened this issue Nov 8, 2024 · 1 comment

Comments

@benjamin051000
Copy link

After running init.sh with default values, running make to see the help text does not appear to format the \ns correctly. I see this in my terminal:

❯ make
\n ------------------------------------------------------------- \n * watch, build and serve the documentation:  make run \n * only build:                                make html \n * only serve:                                make serve \n * clean built doc files:                     make clean-doc \n * clean full environment:                    make clean \n * check links:                               make linkcheck \n * check spelling:                            make spelling \n * check spelling (without building again):   make spellcheck \n * check inclusive language:                  make woke \n * check accessibility:                       make pa11y \n * check style guide compliance:              make vale \n * check style guide compliance on target:    make vale TARGET=* \n * check metrics for documentation:           make allmetrics \n * other possible targets:                    make <TAB twice> \n ------------------------------------------------------------- \n

It appears that using echo -e allows echo to escape newlines properly, but simply modifying the sp-files/Makefile to include this doesn't seem to fix the problem for me, as the generated Makefile is missing the modification. I'm not sure which file needs to be modified.

@benjamin051000
Copy link
Author

See #316 which has a better explanation of the issue.

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