Move the resulting binary to current working directory #2

Closed
opened 2025-08-02 22:31:03 +00:00 by treeshateorcs · 2 comments

I think it would be cool if the result of this command

q build examples/hello

appeared in the directory the command was invoked from, instead of examples/hello

I think it would be cool if the result of this command ``` q build examples/hello ``` appeared in the directory the command was invoked from, instead of `examples/hello`
Owner

I'd need a little more information on why this change would be better as the default.
There are some pros and cons to either way of doing it.

I'm in favor of the current behavior because I can build the same basename in different directories in parallel.
I have a script that invokes the build command on each example/test and binary diffs it with the previous version which requires less directory movement and synchronization using the current behavior.

However (!), one addition that I believe everyone can agree on, is that an explicit -o or --output flag would be very useful.

I'd need a little more information on why this change would be better as the default. There are some pros and cons to either way of doing it. I'm in favor of the current behavior because I can build the same basename in different directories in parallel. I have a script that invokes the build command on each example/test and binary diffs it with the previous version which requires less directory movement and synchronization using the current behavior. However (!), one addition that I believe everyone can agree on, is that an explicit `-o` or `--output` flag would be very useful.
Author

it's just a matter of taste, you are right, there are pros and cons to either way. i thought it was something you had overlooked, but if there are reasons to keep it this way, then it makes sense

it's just a matter of taste, you are right, there are pros and cons to either way. i thought it was something you had overlooked, but if there are reasons to keep it this way, then it makes sense
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
cli/q#2
No description provided.