Skip to content

Conversation

figsoda
Copy link
Contributor

@figsoda figsoda commented Jan 4, 2023

fixes #31

@figsoda figsoda marked this pull request as draft January 5, 2023 00:06
@figsoda
Copy link
Contributor Author

figsoda commented Jan 5, 2023

I will work on it after #189 is out of the way so I don't get merge conflicts

@epage
Copy link
Contributor

epage commented Jan 5, 2023

@figsoda thinking about this more, this is an issue when the user is directly interacting with the program. The current behavior is a bug. What this PR introduces also has bugs. The question is which bug is worse. I think I lean towards the current behavior being worse. What do you think?

If we agree the current behavior is worse, we could possibly merge this now, open a new issue, and then work to get that new issue fixed. This would make it so people have the better experience sooner. Thoughts?

@figsoda figsoda marked this pull request as ready for review January 5, 2023 03:03
@figsoda
Copy link
Contributor Author

figsoda commented Jan 5, 2023

I agree, the current behavior basically fails every single time on TRYCMD=overwrite and doesn't give much information as an interactive command

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

Successfully merging this pull request may close these issues.

A successful overwrite should not fail the run

2 participants