From 2e0a64fd35f6aff7aff1dc2e62aef06dcc490f05 Mon Sep 17 00:00:00 2001
From: Paul Gauthier <aider@paulg.org>
Date: Tue, 16 Jul 2024 16:17:39 +0100
Subject: [PATCH] copy

---
 aider/website/docs/usage/lint-test.md | 27 +++++++++++++++++++++++++++
 1 file changed, 27 insertions(+)

diff --git a/aider/website/docs/usage/lint-test.md b/aider/website/docs/usage/lint-test.md
index a2f53e0c5..08e97b5e5 100644
--- a/aider/website/docs/usage/lint-test.md
+++ b/aider/website/docs/usage/lint-test.md
@@ -26,6 +26,9 @@ command to print them on stdout/stderr
 and return a non-zero exit code.
 This is how most linters normally operate.
 
+By default, aider will lint any files which it edits.
+You can disable this with the `--no-auto-lint` switch.
+
 ## Testing
 
 You can configure aider to run your test suite
@@ -38,6 +41,9 @@ command to print them on stdout/stderr
 and return a non-zero exit code.
 This is how most test tools normally operate.
 
+To have aider automatically run the test command,
+use the `--auto-test` switch.
+
 ## Compiled languages
 
 If you want to have aider compile code after each edit, you
@@ -56,4 +62,25 @@ You could create a small shell script for this.
 Or you may be able to do something as simple as
 `--test-cmd "dotnet build && dotnet test"`.
 
+## Manually running code
+
+You can use the `/run` command in the chat to run your code
+and optionally share the output with aider.
+This can be useful to share error messages or to show aider
+the code's output before asking for changes or corrections.
+
+<div class="chat-transcript" markdown="1">
+> Aider v0.43.5-dev  
+
+#### /run python tmp.py
+
+> Traceback (most recent call last):  
+>  File "myscript.py", line 22, in <module>  
+>    raise ValueError("something bad happened")  
+> ValueError: something bad happened  
+>  
+> Add the output to the chat? y  
+
+</div>
+