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 Custom Target] Always put a space between command and argument #3825

Closed
wants to merge 1 commit into from

Conversation

ntrel
Copy link
Member

@ntrel ntrel commented Apr 8, 2024

Instead of hard coding a space after make for the default command, always put a space.
Before, if the user changes the command, it's easy for them to remove the trailing space, and the argument then gets tacked on to the command name, changing which program is run.

@ntrel ntrel added the build-system Related to the build system(s) label Apr 8, 2024
Copy link
Member

@elextr elextr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The space is currently only added to pre-0.19 formats, so adding it to all formats is an incompatible change. It assumes that the user is typing a full argument as they are required to do pre-0.19 but post 0.19 formats allow them to only have to type part of the argument.

Currently if the user configured "my_build_script f" in the GUI for custom command and typed "oo" the command is "my_build_script foo" but this change will make it "my_build_script f oo" with no way to recover.

@ntrel
Copy link
Member Author

ntrel commented Apr 12, 2024

At least with #3833 it'll be clearer what command gets run.

@ntrel ntrel closed this Apr 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build-system Related to the build system(s)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants