From fea20a6ccef0369c92f30502ec9d91fce924ca59 Mon Sep 17 00:00:00 2001 From: Paul Gauthier Date: Wed, 28 Aug 2024 08:31:57 -0700 Subject: [PATCH] copy --- aider/website/docs/usage/tips.md | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/aider/website/docs/usage/tips.md b/aider/website/docs/usage/tips.md index 8b9d6bb9e..7145e1258 100644 --- a/aider/website/docs/usage/tips.md +++ b/aider/website/docs/usage/tips.md @@ -18,27 +18,26 @@ but be selective. - **Break your goal down into bite sized steps.** Do them one at a time. Adjust the files added to the chat as you go: `/drop` files that don't need any more changes, `/add` files that need changes for the next step. -- For more complex changes, use `/ask` to -[discuss a plan first](modes.html). +- **For complex changes, discuss a plan first** with [the `/ask` command](modes.html). Once you are happy with the approach, just say "go ahead" without the `/ask` prefix. -- Use Control-C to interrupt aider if it isn't providing a useful response. The partial response remains in the conversation, so you can refer to it when you reply with more information or direction. - **If aider gets stuck** trying to make a change, try: - - Using `/clear` to discard the chat history and make a fresh start. + - Use `/clear` to discard the chat history and make a fresh start. - Can you `/drop` any extra files? - - Consider using `/ask` to discuss a plan before aider codes. + - Use `/ask` to discuss a plan before aider starts editing code. - If aider is hopelessly stuck, just code the next step yourself and try having aider code some more after that. -Pair program with aider. +Take turns and pair program with aider. - If your code is throwing an error, -use the `/run` [in-chat command](commands.html) +use the [`/run` command](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](commands.html) +- If test are failing, use the [`/test` command](commands.html) to run tests and share the error output with the aider. - LLMs know about a lot of standard tools and libraries, but may get some of the fine details wrong about API versions and function arguments. You can paste doc snippets into the chat or include a URL to docs in your chat message. Aider will scrape and read the URL. +- Use Control-C to interrupt aider if it isn't providing a useful response. The partial response remains in the conversation, so you can refer to it when you reply with more information or direction. - {% include multi-line.md %}