mirror of
https://github.com/Aider-AI/aider.git
synced 2025-06-02 18:54:59 +00:00
moved files to usage/
This commit is contained in:
parent
59b3b6da0f
commit
47961ef207
8 changed files with 4 additions and 3 deletions
|
@ -43,7 +43,8 @@ for additional information.
|
|||
|
||||
## Enable voice coding
|
||||
|
||||
Aider supports [coding with your voice](https://aider.chat/docs/voice.html)
|
||||
Aider supports
|
||||
[coding with your voice](https://aider.chat/docs/usage/voice.html)
|
||||
using the in-chat `/voice` command.
|
||||
Aider uses the [PortAudio](http://www.portaudio.com) library to
|
||||
capture audio.
|
||||
|
|
|
@ -14,10 +14,10 @@ So the LLM can see all the other relevant parts of your code base.
|
|||
- Large changes are best performed as a sequence of thoughtful bite sized steps, where you plan out the approach and overall design. Walk the LLM through changes like you might with a junior dev. Ask for a refactor to prepare, then ask for the actual change. Spend the time to ask for code quality/structure improvements.
|
||||
- Use Control-C to safely interrupt the LLM if it isn't providing a useful response. The partial response remains in the conversation, so you can refer to it when you reply to the LLM with more information or direction.
|
||||
- If your code is throwing an error,
|
||||
use the `/run` [in-chat command](/docs/commands.html)
|
||||
use the `/run` [in-chat command](/docs/usage/commands.html)
|
||||
to share the error output with the aider.
|
||||
Or just paste the errors into the chat. Let the aider figure out and fix the bug.
|
||||
- If test are failing, use the `/test` [in-chat command](/docs/commands.html)
|
||||
- If test are failing, use the `/test` [in-chat command](/docs/usage/commands.html)
|
||||
to run tests and
|
||||
share the error output with the aider.
|
||||
- {% include multi-line.md %}
|
Loading…
Add table
Add a link
Reference in a new issue