fix(Windows): Nushell integration

[john-trieu-nguyen]

let exe = opts.exe.display().to_string();
display() on Windows outputs backslashes eg. "C:\Users\john"

Nushell treats backslashes in double-quoted strings as escape characters.

You get this error when running fnox in nushell on Windows:
unrecognized escape after "\" in string

Update opts.exe.display to use
.to_string_lossy().replace('\\', "/");
fixes issue.

[greptile-apps]

Greptile Summary

This PR fixes a Windows-specific Nushell integration bug where display() produced backslash-separated paths (e.g. C:\Users\john\fnox.exe) that Nushell interpreted as escape sequences inside double-quoted strings. The fix replaces display().to_string() with to_string_lossy().replace('\\', "/"), converting backslashes to forward slashes (which Windows accepts) before the path is embedded in the generated Nushell script.

Confidence Score: 5/5

Safe to merge — the fix is minimal, correct, and addresses the prior review concern about single-quoted strings.

The approach of converting backslashes to forward slashes is robust: Windows accepts forward slashes in all standard path contexts, UNC paths (//server/share) are also valid on Windows, and the exe path remains inside double-quoted Nushell strings so spaces and other characters are still correctly handled. No P1 or P0 issues remain.

No files require special attention.

Important Files Changed

Filename	Overview
src/shell/nushell.rs	Replaces backslashes with forward slashes in the exe path to fix Nushell double-quoted string escape errors on Windows; no issues found.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["opts.exe PathBuf"] --> B["to_string_lossy()"]
    B --> C["replace backslash with forward-slash"]
    C --> D["exe: C:/Users/john/fnox.exe"]
    D --> E["Embedded in Nushell double-quoted strings"]
    E --> F["No escape errors in Nushell on Windows"]

Loading

_{Reviews (2): Last reviewed commit: "update path output to not have backslash..." | Re-trigger Greptile}

[gemini-code-assist]

Code Review

This pull request modifies the Nushell shell integration by replacing double quotes with single quotes for the executable path template. While this change likely aims to resolve backslash escaping issues on Windows, feedback indicates it introduces a regression for file paths containing apostrophes, as Nushell single-quoted strings are raw and cannot escape single quotes. It is recommended to normalize the path using forward slashes and revert to double quotes for better compatibility.