AI search engine and MCP server for bots and agents. One Rust binary indexes code, docs, logs, JSONL/CSV and PDFs for BM25 full-text, vector and hybrid search, code search without grep, agent memory and RAG. Elasticsearch-compatible API; Corpus Hub serves hundreds of reference memory corpora.
Rust agent-memoryai-agentsbm25claude-codeclicode-searchcursordatabaseelasticsearchfull-text-searchhybrid-searchjsonllocal-firstmcpmcp-servermodel-context-protocolragrustsearch-enginevector-search
fix(docs): name both Windows install directories (#2285) (#2289)
xerj-orgbbf80c0984d6
diff --git a/AGENTS.md b/AGENTS.mdindex 3e3b32db9..d5e006336 100644--- a/AGENTS.md+++ b/AGENTS.md@@ -166,7 +166,7 @@ that is already running; it does not start one.}```-Use an absolute path (`command -v xerj`): MCP hosts started from a desktop icon+Use an absolute path (`command -v xerj`; PowerShell: `(Get-Command xerj).Source`). The `sh` installer, including Windows Git Bash, MSYS and Cygwin, puts `xerj.exe` in `~/.local/bin` and does not edit PATH. The PowerShell installer (`get.ps1`) puts `xerj.exe` in `%LOCALAPPDATA%\Programs\xerj` and adds that directory to the user PATH. MCP hosts started from a desktop icondo not inherit a shell `PATH`. Add `"XERJ_AUTH": "ApiKey <key>"` when the nodeis not running `--insecure` — the key is `<data-dir>/admin.key`. `--url` and`--auth` flags override the two environment variables.diff --git a/README.md b/README.mdindex 2e5599346..56e4edf66 100644--- a/README.md+++ b/README.md@@ -332,8 +332,7 @@ boots the same `--insecure` dev node. Drop this into your MCP client's config:}```-Use an absolute path. The installer puts `xerj` in `~/.local/bin` by default-(`command -v xerj` confirms), and MCP hosts launched from a desktop icon do not inherit your+Use an absolute path. The `sh` installer (Linux, macOS, and Windows Git Bash, MSYS and Cygwin) puts `xerj` in `~/.local/bin` (`xerj.exe` on Windows; `command -v xerj` confirms) and does not edit PATH. The PowerShell installer (`get.ps1`) puts `xerj.exe` in `%LOCALAPPDATA%\Programs\xerj` and adds that directory to the user PATH (`(Get-Command xerj).Source` confirms; `XERJ_NO_PATH=1` opts out). MCP hosts launched from a desktop icon do not inherit yourshell's `PATH`. If the node is running with auth (anything but `--insecure`), add`"XERJ_AUTH": "ApiKey <key>"` alongside `XERJ_URL`; the key is in `<data-dir>/admin.key`.diff --git a/engine/crates/xerj-common/tests/windows_install_path.rs b/engine/crates/xerj-common/tests/windows_install_path.rsindex cc6dec1ef..03d019503 100644--- a/engine/crates/xerj-common/tests/windows_install_path.rs+++ b/engine/crates/xerj-common/tests/windows_install_path.rs@@ -1,5 +1,8 @@-//! `get.ps1` installs to `%LOCALAPPDATA%\Programs\xerj`. The install page-//! used to state the only default as `~/.local/bin`, which is the Unix path.+//! Two Windows installers, two directories. `landing/get` (the `sh` installer,+//! including Git Bash / MSYS / Cygwin) writes `xerj.exe` to `~/.local/bin`.+//! `landing/get.ps1` writes it to `%LOCALAPPDATA%\Programs\xerj` and adds that+//! directory to the user PATH. Docs that name only the PowerShell directory+//! send a Git Bash install looking in the wrong place (#2285).use std::path::PathBuf;@@ -10,22 +13,77 @@ fn repo(rel: &str) -> String {std::fs::read_to_string(&path).unwrap_or_else(|e| panic!("read {}: {e}", path.display()))}+/// Pages and agent-facing files that state where the binary lands.+const INSTALL_PATH_DOCS: &[&str] = &[+ "landing/docs/install.html",+ "landing/docs/agents/quickstart.html",+ "landing/docs/cli.html",+ "landing/llms.txt",+ "README.md",+ "AGENTS.md",+];+#[test]-fn install_docs_name_the_windows_default_directory() {- let needle = "%LOCALAPPDATA%\\Programs\\xerj";- for rel in [- "landing/docs/install.html",- "landing/docs/agents/quickstart.html",- "landing/docs/cli.html",- ] {+fn install_docs_name_both_windows_installers() {+ let ps_dir = "%LOCALAPPDATA%\\Programs\\xerj";+ for rel in INSTALL_PATH_DOCS {let text = repo(rel);assert!(- text.contains(needle),- "{rel} must name the Windows install directory {needle}"+ text.contains(ps_dir),+ "{rel} must name the PowerShell install directory {ps_dir}");assert!(text.contains("~/.local/bin"),- "{rel} must keep the Linux and macOS default"+ "{rel} must name the sh installer's directory, including on Windows Git Bash"+ );+ assert!(+ text.contains("Git Bash"),+ "{rel} must say the sh installer on Git Bash uses ~/.local/bin, not only the PowerShell path"+ );+ assert!(+ text.contains("PowerShell") || text.contains("get.ps1"),+ "{rel} must name the PowerShell installer that uses {ps_dir}");}}++#[test]+fn shell_installer_uses_home_local_bin_including_on_windows() {+ let sh = repo("landing/get");+ assert!(+ sh.contains("MINGW*|MSYS*|CYGWIN*"),+ "the sh installer must recognise Git Bash / MSYS / Cygwin"+ );+ assert!(+ sh.contains("bin=\"xerj.exe\""),+ "Windows via the sh installer installs xerj.exe"+ );+ assert!(+ sh.contains("dir=\"$HOME/.local/bin\""),+ "the sh installer's default directory is ~/.local/bin on every OS it supports"+ );+ // Comments may name the PowerShell directory so a later edit does not+ // retarget this script. The executable lines must not.+ let code: String = sh+ .lines()+ .filter(|l| !l.trim_start().starts_with('#'))+ .collect::<Vec<_>>()+ .join("\n");+ assert!(+ !code.contains("LOCALAPPDATA"),+ "the sh installer must not install to %LOCALAPPDATA%; that directory is get.ps1 only"+ );+}++#[test]+fn powershell_installer_uses_localappdata_programs() {+ let ps1 = repo("landing/get.ps1");+ assert!(+ ps1.contains("Join-Path $env:LOCALAPPDATA 'Programs\\xerj'"),+ "get.ps1 must keep its default of %LOCALAPPDATA%\\Programs\\xerj"+ );+ assert!(+ ps1.contains("XERJ_NO_PATH"),+ "get.ps1 adds the install directory to the user PATH unless XERJ_NO_PATH is set"+ );+}diff --git a/engine/crates/xerj-mcp/src/lib.rs b/engine/crates/xerj-mcp/src/lib.rsindex ef86fdef2..c331d11bf 100644--- a/engine/crates/xerj-mcp/src/lib.rs+++ b/engine/crates/xerj-mcp/src/lib.rs@@ -184,10 +184,14 @@ MCP CLIENT CONFIG (Claude Desktop, IDE agents, any mcpServers-shaped config):}}-Use an ABSOLUTE path — `command -v xerj` prints it, and the installer's-default is ~/.local/bin/xerj. An MCP host launched from a desktop icon does-not inherit your shell's PATH, so a bare \"xerj\" fails there with no useful-error. When the node is not running --insecure, add+Use an ABSOLUTE path — `command -v xerj` prints it (PowerShell:+`(Get-Command xerj).Source`). The sh installer (https://xerj.org/get,+including Git Bash, MSYS and Cygwin) puts the binary in ~/.local/bin+(xerj.exe on Windows) and does not edit PATH. The PowerShell installer+(get.ps1) puts xerj.exe in %LOCALAPPDATA%\\Programs\\xerj and adds that+directory to the user PATH (opt out: XERJ_NO_PATH=1). An MCP host launched+from a desktop icon does not inherit your shell's PATH, so a bare \"xerj\"+fails there with no useful error. When the node is not running --insecure, add\"XERJ_AUTH\": \"ApiKey <key>\" beside XERJ_URL; the key is <data-dir>/admin.key.For a loopback node (localhost / 127.0.0.1 / [::1]) that step is optional:with no XERJ_AUTH given, the server reads <data-dir>/admin.key itself (the@@ -5288,6 +5292,30 @@ mod tests {assert!(help.contains("serves 3 Corpus Hub tools"), "{help}");}+ /// #2285: Git Bash runs the `sh` installer, which writes `~/.local/bin`.+ /// `get.ps1` writes `%LOCALAPPDATA%\Programs\xerj`. Help that names only+ /// one of those sends the other install looking in the wrong place.+ #[test]+ fn help_names_both_windows_install_locations() {+ let help = help_text(false);+ assert!(+ help.contains("~/.local/bin"),+ "sh installer directory missing:\n{help}"+ );+ assert!(+ help.contains("%LOCALAPPDATA%\\Programs\\xerj"),+ "PowerShell installer directory missing:\n{help}"+ );+ assert!(+ help.contains("Git Bash"),+ "help must say Git Bash / the sh installer uses ~/.local/bin:\n{help}"+ );+ assert!(+ help.contains("get.ps1") || help.contains("PowerShell"),+ "help must name the PowerShell installer:\n{help}"+ );+ }+/// #1055: the field map is an orientation tool an agent calls before it/// writes DSL — its description must say what to reach for, what the/// facts ARE (sampled, not exhaustive), and how the byte cap trims.diff --git a/landing/docs/agents/quickstart.html b/landing/docs/agents/quickstart.htmlindex d320cebe4..1129302d4 100644--- a/landing/docs/agents/quickstart.html+++ b/landing/docs/agents/quickstart.html@@ -231,7 +231,7 @@<p>Five steps, all runnable, all on port <code class="inline">9200</code>: <strong>boot XERJ → check it is up → store a memory → recall it by meaning → run a semantic search.</strong> Every request and every response below is a real run against a freshly booted, empty XERJ — no seeding, no external embedding service, no API key. If you have <code class="inline">curl</code>, you have everything.</p><h2>0 · Boot XERJ</h2>- <p>One binary. <code class="inline">--insecure</code> disables TLS and API-key auth so you can talk to it over plain HTTP on the default ES-compat port <code class="inline">9200</code> — perfect for a local agent loop. Install it first (<code class="inline">curl -fsSL https://xerj.org/get | sh</code> on Linux and macOS, <code class="inline">irm https://xerj.org/get.ps1 | iex</code> on Windows). The Unix installer puts <code class="inline">xerj</code> in <code class="inline">~/.local/bin</code> and prints the exact path if that is not on your <code class="inline">PATH</code>. The Windows installer puts it in <code class="inline">%LOCALAPPDATA%\Programs\xerj</code>.</p>+ <p>One binary. <code class="inline">--insecure</code> disables TLS and API-key auth so you can talk to it over plain HTTP on the default ES-compat port <code class="inline">9200</code> — perfect for a local agent loop. Install it first (<code class="inline">curl -fsSL https://xerj.org/get | sh</code> on Linux, macOS, and Windows Git Bash, MSYS and Cygwin; <code class="inline">irm https://xerj.org/get.ps1 | iex</code> in PowerShell). The <code class="inline">sh</code> installer puts <code class="inline">xerj</code> in <code class="inline">~/.local/bin</code> (<code class="inline">xerj.exe</code> on Windows) and prints the exact path if that is not on your <code class="inline">PATH</code>. The PowerShell installer puts <code class="inline">xerj.exe</code> in <code class="inline">%LOCALAPPDATA%\Programs\xerj</code> and adds that directory to the user PATH.</p><pre class="code"># start it in the background — a foreground boot blocks the rest of this page$ xerj --insecure --data-dir /tmp/xerj-agent &diff --git a/landing/docs/cli.html b/landing/docs/cli.htmlindex 070366a2b..44e542a32 100644--- a/landing/docs/cli.html+++ b/landing/docs/cli.html@@ -479,7 +479,7 @@ OPTIONS:}}</pre>- <p>Use an <em>absolute</em> path — the installer puts <code class="inline">xerj</code> in <code class="inline">~/.local/bin</code> on Linux and macOS (<code class="inline">command -v xerj</code> confirms) and in <code class="inline">%LOCALAPPDATA%\Programs\xerj</code> on Windows, and an MCP host launched from a desktop icon does not inherit your shell's <code class="inline">PATH</code>. When the node is not running <code class="inline">--insecure</code>, add <code class="inline">"XERJ_AUTH": "ApiKey <key>"</code> next to <code class="inline">XERJ_URL</code>; the key lives in <code class="inline"><data-dir>/admin.key</code>. For a loopback node that manual step is optional: with no <code class="inline">XERJ_AUTH</code> given, the server reads <code class="inline"><data-dir>/admin.key</code> itself (the same locations <code class="inline">xerj autoindex</code> checks) and announces the file it used on stderr — it never does this for a non-loopback URL.</p>+ <p>Use an <em>absolute</em> path. The <code class="inline">sh</code> installer (Linux, macOS, and Windows Git Bash, MSYS and Cygwin) puts <code class="inline">xerj</code> in <code class="inline">~/.local/bin</code> (<code class="inline">xerj.exe</code> on Windows; <code class="inline">command -v xerj</code> confirms) and does not edit PATH. The PowerShell installer (<code class="inline">get.ps1</code>) puts <code class="inline">xerj.exe</code> in <code class="inline">%LOCALAPPDATA%\Programs\xerj</code> and adds that directory to the user PATH (<code class="inline">(Get-Command xerj).Source</code> prints it; <code class="inline">XERJ_NO_PATH=1</code> opts out). An MCP host launched from a desktop icon does not inherit your shell's <code class="inline">PATH</code>. When the node is not running <code class="inline">--insecure</code>, add <code class="inline">"XERJ_AUTH": "ApiKey <key>"</code> next to <code class="inline">XERJ_URL</code>; the key lives in <code class="inline"><data-dir>/admin.key</code>. For a loopback node that manual step is optional: with no <code class="inline">XERJ_AUTH</code> given, the server reads <code class="inline"><data-dir>/admin.key</code> itself (the same locations <code class="inline">xerj autoindex</code> checks) and announces the file it used on stderr — it never does this for a non-loopback URL.</p><h3 id="mcp-clients">Supported agents</h3>diff --git a/landing/docs/install.html b/landing/docs/install.htmlindex ff8ca12d8..cb89488af 100644--- a/landing/docs/install.html+++ b/landing/docs/install.html@@ -251,10 +251,11 @@<pre class="code">$ curl -fsSL https://xerj.org/get | sh</pre><p><strong>Windows</strong> (x64 and ARM64, PowerShell):</p><pre class="code">> powershell -ExecutionPolicy Bypass -c "irm https://xerj.org/get.ps1 | iex"</pre>+ <p>That PowerShell installer puts <code class="inline">xerj.exe</code> in <code class="inline">%LOCALAPPDATA%\Programs\xerj</code> and adds that directory to the user PATH (opt out with <code class="inline">XERJ_NO_PATH=1</code>; open a new terminal). Git Bash, MSYS and Cygwin run the same <code class="inline">curl | sh</code> line as Linux and macOS. That installer puts <code class="inline">xerj.exe</code> in <code class="inline">~/.local/bin</code> and does not edit PATH. Re-run the installer you used to upgrade: the two write different directories.</p><p>Both installers verify <strong>fail-closed</strong>: each computes the archive's own SHA-256 and compares it against the published digest, and if the checksum cannot be downloaded, or no SHA-256 tool (<code class="inline">sha256sum</code>, <code class="inline">shasum</code>, <code class="inline">openssl</code>, <code class="inline">busybox</code>…) can be found, the installer stops rather than installing an unverified binary.</p><p>On Linux the one-liner installs the <strong>static musl</strong> build by default — it runs on any distro including Alpine and has no glibc-version floor. Ask for the glibc build explicitly if you need it:</p><pre class="code">$ curl -fsSL https://xerj.org/get | XERJ_LIBC=gnu sh</pre>- <p>Other environment overrides: <code class="inline">XERJ_VERSION</code> (install a specific tag), <code class="inline">XERJ_INSTALL_DIR</code> (default <code class="inline">~/.local/bin</code> on Linux and macOS, <code class="inline">%LOCALAPPDATA%\Programs\xerj</code> on Windows), <code class="inline">XERJ_REPO</code>.</p>+ <p>Other environment overrides: <code class="inline">XERJ_VERSION</code> (install a specific tag), <code class="inline">XERJ_INSTALL_DIR</code> (the <code class="inline">sh</code> installer, including Git Bash, MSYS and Cygwin, defaults to <code class="inline">~/.local/bin</code>; the PowerShell installer defaults to <code class="inline">%LOCALAPPDATA%\Programs\xerj</code>), <code class="inline">XERJ_REPO</code>.</p><h2>Manual download</h2><p>Every release publishes eight targets, each with a <code class="inline">.sha256</code> alongside: <code class="inline">x86_64</code>/<code class="inline">aarch64</code> × <code class="inline">unknown-linux-musl</code> (static, any distro), <code class="inline">unknown-linux-gnu</code>, <code class="inline">apple-darwin</code>, and <code class="inline">pc-windows-msvc</code> (.zip).</p>diff --git a/landing/get b/landing/getindex e2886a4cf..d9dd0f292 100644--- a/landing/get+++ b/landing/get@@ -214,6 +214,10 @@ src="${tmp}/${stage}/${bin}"chmod +x "$src" 2>/dev/null || true# --- choose install dir -----------------------------------------------------+# Same default on every OS this script supports, including Windows Git Bash /+# MSYS / Cygwin (the file there is xerj.exe). The PowerShell installer+# (get.ps1) is the one that uses %LOCALAPPDATA%\Programs\xerj. Do not special-+# case Windows here: a Git Bash `curl | sh` is this script, not get.ps1.# Re-testing -w AFTER the mkdir matters: mkdir -p on an EXISTING but# root-owned ~/.local/bin returns 0, and we must fall through to $(pwd)# instead of failing later at the copy.diff --git a/landing/get.ps1 b/landing/get.ps1index 670376bdb..125777eb1 100644--- a/landing/get.ps1+++ b/landing/get.ps1@@ -9,6 +9,8 @@# Environment overrides:# XERJ_VERSION=v1.0.0 install a specific tag (default: latest release)# XERJ_INSTALL_DIR=path install location (default: %LOCALAPPDATA%\Programs\xerj)+# The sh installer (landing/get), including Git Bash,+# MSYS and Cygwin, uses ~/.local/bin instead.# XERJ_REPO=owner/name source repo (default: xerj-org/xerj)# XERJ_NO_PATH=1 do not add the install dir to the user PATH#diff --git a/landing/llms.txt b/landing/llms.txtindex 131de6fef..ea7ad2666 100644--- a/landing/llms.txt+++ b/landing/llms.txt@@ -1,6 +1,6 @@# XERJ-Last updated: 2026-10-21 (hub section run on v1.0.0-rc.97). When this file and the binary disagree, the binary wins: `xerj --help` and `xerj <command> --help` outrank this file and every page it links.+Last updated: 2026-10-23 (Windows install paths; hub section run on v1.0.0-rc.97). When this file and the binary disagree, the binary wins: `xerj --help` and `xerj <command> --help` outrank this file and every page it links.> **This file is an index for you, the AI agent: search it for your topic and follow the link — the detail lives behind the links, not here.** XERJ is an AI-native search engine in a single Rust binary. `xerj autoindex <folder>` turns mixed-format files (PDF, DOCX, SQLite, hostile CSVs, logs, SQL dumps, mbox mailboxes, …) into typed, queryable, self-describing indices with zero configuration; agents then query them over an Elasticsearch-8.x-compatible REST API with first-class agent primitives — semantic search, kNN vector search, hybrid retrieval, and namespaced long-term memory. No JVM, no separate vector DB, no embedding API key: a zero-config embedder ships inside the binary. ES wire compatibility is the transport, not the product. Expanded capability and API reference: [llms-full.txt](https://xerj.org/llms-full.txt).@@ -13,9 +13,9 @@ This file asks two things of you. **Reference-code before you write** — retrie- Linux / macOS: `curl -fsSL https://xerj.org/get | sh`- Windows PowerShell: `irm https://xerj.org/get.ps1 | iex`-The installer detects OS/CPU (Linux x86_64/aarch64 static musl, macOS x86_64/arm64, Windows x64/ARM64; the x86_64 builds target x86-64-v2 and use AVX2/FMA at runtime when the CPU has them, so a pre-Haswell CPU installs and runs the same binary), downloads the latest GitHub release, verifies its SHA-256 (fail-closed: a missing or mismatched checksum aborts, and the `sh` installer tries `sha256sum`, `shasum`, `openssl`, `sha256`, `busybox` and `cksum` in turn and **refuses to install** if none exists — installing unverified is opt-in only, with `XERJ_INSECURE_SKIP_CHECKSUM=1`), and installs one `xerj` binary — default `~/.local/bin` on Unix (it prints the path and a PATH hint; it does not edit your shell profile), `%LOCALAPPDATA%\Programs\xerj` on Windows (added to user PATH; opt out with `XERJ_NO_PATH=1`). Pin with `XERJ_VERSION=vX.Y.Z`; both honour `XERJ_INSTALL_DIR`.+The installer detects OS/CPU (Linux x86_64/aarch64 static musl, macOS x86_64/arm64, Windows x64/ARM64; the x86_64 builds target x86-64-v2 and use AVX2/FMA at runtime when the CPU has them, so a pre-Haswell CPU installs and runs the same binary), downloads the latest GitHub release, verifies its SHA-256 (fail-closed: a missing or mismatched checksum aborts, and the `sh` installer tries `sha256sum`, `shasum`, `openssl`, `sha256`, `busybox` and `cksum` in turn and **refuses to install** if none exists — installing unverified is opt-in only, with `XERJ_INSECURE_SKIP_CHECKSUM=1`), and installs one `xerj` binary. The `sh` installer (Linux, macOS, and Windows Git Bash, MSYS and Cygwin) defaults to `~/.local/bin` (`xerj.exe` on Windows; it prints the path and a PATH hint and does not edit your shell profile). The PowerShell installer (`get.ps1`) defaults to `%LOCALAPPDATA%\Programs\xerj` and adds that directory to the user PATH (opt out with `XERJ_NO_PATH=1`). Pin with `XERJ_VERSION=vX.Y.Z`; both honour `XERJ_INSTALL_DIR`.-**PATH consequence — read this before the next command.** Because the installer does not edit your shell profile, in a fresh shell `~/.local/bin` is often not on `PATH` and a bare `xerj …` fails with `command not found`. Either call it by full path (`$HOME/.local/bin/xerj …`) or `export PATH="$HOME/.local/bin:$PATH"` first. Every `xerj` below assumes you did one of those.+**PATH consequence — read this before the next command.** Because the `sh` installer does not edit your shell profile, in a fresh shell `~/.local/bin` is often not on `PATH` and a bare `xerj …` fails with `command not found`. The PowerShell installer does add its directory to the user PATH; a new terminal picks that up. Either call it by full path (`$HOME/.local/bin/xerj …`) or `export PATH="$HOME/.local/bin:$PATH"` first. Every `xerj` below assumes you did one of those.First run, in order (`autoindex` is a client of a running node at `http://localhost:9200`):diff --git a/landing/product.html b/landing/product.htmlindex 170998112..d03c43183 100644--- a/landing/product.html+++ b/landing/product.html@@ -213,7 +213,7 @@<div class="kicker"><span class="accent">02</span><span class="dash">·</span><span>QUICKSTART</span></div><h2 class="scene">INSTALL, INDEX,<br><span class="accent">ASK.</span></h2>- <p class="wide">The installer at <a href="/get">xerj.org/get</a> picks the release for your OS and CPU, checks its SHA-256, and puts <code class="inline">xerj</code> on <code class="inline">~/.local/bin</code>. On Linux the default archive is the static musl build. <code class="inline">xerj --version</code> on that binary, run 2026-10-23, printed <span class="mono">xerj v1.0.0-rc.98</span>.</p>+ <p class="wide">The installer at <a href="/get">xerj.org/get</a> picks the release for your OS and CPU, checks its SHA-256, and puts <code class="inline">xerj</code> on <code class="inline">~/.local/bin</code> (<code class="inline">xerj.exe</code> there under Git Bash, MSYS or Cygwin). PowerShell's installer (<a href="/get.ps1">get.ps1</a>) puts <code class="inline">xerj.exe</code> in <code class="inline">%LOCALAPPDATA%\Programs\xerj</code> instead. On Linux the default archive is the static musl build. <code class="inline">xerj --version</code> on that binary, run 2026-10-23, printed <span class="mono">xerj v1.0.0-rc.98</span>.</p><pre class="code">curl -fsSL https://xerj.org/get | shxerj --insecure --data-dir ~/xerj-data & <span class="comment"># node on 127.0.0.1:9200</span>