-
Notifications
You must be signed in to change notification settings - Fork 1k
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
When aider tries to create *.py file it throws OSError on Windows #603
Comments
Thanks for trying aider and filing this issue. When you run with What are you trying to do? Why are you running with |
In this case I forgot I was in a parent folder so I needed to do /add backend/*.py instead. What I would expect is that it doesn’t even ask to create a file with a wildcard because that is never possible. Second best case would be to catch the error so it just keeps the session alive even if that operation does nothing. On May 16, 2024, at 8:56 AM, paul-gauthier ***@***.***> wrote:
Thanks for trying aider and filing this issue.
When you run with --yes aider will answer yes to every question. Sometimes that will cause unexpected actions to occur.
What are you trying to do? Why are you running with --yes and then typing /add *.py when there are no python files?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Ah yes, you're right. Aider should catch the FYI, on non-Windows, you can make files with wildcards in their names. |
Aider fixed this issue. The change is available in the main branch. You can get it by installing the latest version from github:
If you have a chance to try it, let me know if it works better for you. |
Issue
The text was updated successfully, but these errors were encountered: