summaryrefslogtreecommitdiff
path: root/docs/usage-examples.md
diff options
context:
space:
mode:
authorPaul Buetow <paul@buetow.org>2025-08-28 23:39:23 +0300
committerPaul Buetow <paul@buetow.org>2025-08-28 23:39:23 +0300
commit1e5718bc44064481d33a0fc3247c345305d3ba86 (patch)
tree7b6b32153331492eb19b522f3e05fc690ded508b /docs/usage-examples.md
parent86aafe22eaf04687288e5a730acf0a473719c514 (diff)
lsp: switch in-editor chat triggers to ?> !> :> ;> and suppress normal completion on EOL chat trigger; keep ;;text; inline trigger unchanged; update docs and tests
Diffstat (limited to 'docs/usage-examples.md')
-rw-r--r--docs/usage-examples.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/usage-examples.md b/docs/usage-examples.md
index aa8205f..5a80b18 100644
--- a/docs/usage-examples.md
+++ b/docs/usage-examples.md
@@ -32,8 +32,8 @@ Note: additional LSPs (`gopls`, `golangci-lint-lsp`) are optional; Hexai works w
Ask a question at the end of a line and receive the answer inline.
-- End your question line with a trigger: `??`, `!!`, or `::`.
-- Hexai removes the trailing marker (last char for `??`/`!!`/`::`, both for `;;`).
+- End your question line with a trigger: `?>`, `!>`, or `:>`.
+- Hexai removes only the trailing `>` from the question line (and keeps your trailing punctuation). The inline code-completion trigger `;;text;` remains unchanged.
- It inserts a blank line, then a reply line prefixed with `> `, then one extra newline so most
editors place the cursor on a fresh blank line after the answer.
- If a `>` reply already exists below the question, Hexai won’t answer again.
@@ -41,7 +41,7 @@ Ask a question at the end of a line and receive the answer inline.
Example:
```text
-What is a slice in Go??
+What is a slice in Go?>
> A slice is a dynamically-sized, flexible view into the elements of an array. It references
> an underlying array and tracks length/capacity; most Go code uses slices instead of arrays.