-
Notifications
You must be signed in to change notification settings - Fork 2.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
Terminal output in VSCode is broken #124
Comments
Thanks for trying aider and reporting this issue. You might want to try running with |
I asked aider to disable pretty if it detects that it is running inside a VSCode terminal. I've merged a fix into 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. |
I'm going to close this issue for now, but feel free to re-open or file a new issue any time. |
@paul-gauthier Any plans for a permanenet fix for this? |
As far as I can tell the problem is that vscode doesn't provide a fully capable terminal. Aider should be turning off fancy output when run inside vscode. Is that not working for you? |
hmmm... so it's a limitation in the vscode terminal vs aider. I was thinking it might be related to the rich library, so I was hoping it would be fixed soon. aider does turn off the fancy output, which works as a workaround; however, it makes the output hard to read, so I'm not a big fan of it. |
You can always run aider in a real terminal window beside your vscode window. |
Hi there,
and first of: thanks a LOT for creating this awesome AI helper! It's really like having your senior developer live right in your Git repo - truly amazing!
I did notice, though, that the output in the VSCode terminal is "broken" in the sense that it repeatedly lists the same chunks of prose and code over and over again. I think it happens each time there's code involved:
The text was updated successfully, but these errors were encountered: