What is different in the desktop app on Windows — the SmartScreen warning, the card before every command, allowing a command for the session, and contained commands with WSL.

On this page

The desktop app supports Windows from version 1.1.0. Everything in these pages applies, with the differences below.

Installing: the SmartScreen warning#

The Windows installer isn't signed yet, so SmartScreen shows "Windows protected your PC" with an unknown publisher. Choose More info → Run anyway.

The installer works for your user, lets you choose the folder, and adds Open in Ysra to the right-click menu for folders. Full steps: Install the desktop app.

How commands work on Windows#

On macOS and Linux I run commands contained to your folder. Windows has no equivalent, so there commands aren't contained, and I ask before every one.

Run this command?
  npm test
  in C:\code\billing-service
Commands on Windows aren't contained: this can reach the network and anything
your account can.
  [Run once]  [Allow `npm test` for this session]  [Don't run]
Answer What it does
Run once Runs this command, this time
Allow … for this session Runs it, and the same command again in this session without asking
Don't run I don't run it, and I don't try it again
  • A shell or inline code (cmd, powershell, python -c, node -e) can only ever be run once. It is never allowed for the session, because it could run anything.
  • No answer within 15 minutes counts as Don't run.
  • Auto mode never answers this.
  • Stopping ends everything a command started.

Read the command and the folder before you answer. What I say about commands being contained elsewhere in these docs applies to macOS, Linux and WSL, not to plain Windows.

Contained commands with WSL#

If you have WSL, I can run commands inside it, contained to your folder as on Linux, with no card for each one.

  1. Install WSL yourself if you don't have it (wsl --install in PowerShell). I never install it for you.
  2. Inside WSL, install what I need:

    sudo apt install bubblewrap socat ripgrep
    
  3. Turn it on (see below).

Your project's tools then have to exist inside WSL too: Node.js, Python and so on are the WSL ones, not the Windows ones.

Other Windows behaviour#

  • Files keep their line endings. A CRLF file stays CRLF; an LF file stays LF.
  • I refuse names Windows treats specially, such as CON.txt or a name ending in a dot, and I won't work on a drive root or on C:\Users itself. Pick the project folder.

Turn WSL on or off#

Settings → General shows which way commands run:

Settings shows Meaning
Commands: need your OK (not contained) Every command shows a card
Commands: contained (WSL) Commands run inside WSL, contained, without a card

Use the switch beside it. Set up walks you through what WSL still needs. The first time a command card appears and WSL is ready, I offer once to switch.

Smaller differences#

  • Use Ctrl wherever these pages show Cmd.
  • Closing the window keeps Ysra running in the tray; choose Quit Ysra from the tray to stop it.
  • Right-click a folder and choose Open in Ysra to start a thread on it.
YsraDocs