2 ms·

Can you fix the CLI on Windows? You broke it a few versions ago. 'zed --version' and all the other flags don't work. Maybe broken command parser or something, i

Can you fix the CLI on Windows? You broke it a few versions ago. 'zed --version' and all the other flags don't work. Maybe broken command parser or something, im not sure. Zed with zero flags still launches it. I particularly want to be able to pass it filenames for quick opening and --new and --wait. Used to work. Thanks!

miguelraz 6mo ago
Zed support engineer here, that sounds like a bug! I have `zed --version` working on my Windows machine: PS C:\WINDOWS\system32> zed --version Zed 1.0.0 5ec84a926ef83865afb92d2a3d1ca3b419572cf9 – \\?\C:\Users\mrg\AppData\Local\Programs\Zed\Zed.exe If you're up for it, we can pair next week to get a proper bug report filed https://calendar.app.google/qPgW7q6upb3RqPjx5 https://calendar.app.google/qPgW7q6upb3RqPjx5
- hdjrudni 6mo ago
  I wasn't expecting that level of support, thanks for the offer! You said it should work, so I did some poking around. Uninstalled it, reinstalled it. Still didn't work. The "About" in app said I was running 1.0.0+stable Checked my environment paths and saw I had both C:\Users\Me\AppData\Local\Programs\Zed C:\Users\Me\AppData\Local\Programs\Zed\bin So I opened those paths in explorer, and there is indeed a zed.exe in both dirs. So I tried them explicitly: Me@DESKTOP-NN7TD9I ~ $ "C:\Users\Me\AppData\Local\Programs\Zed\Zed.exe" --help Me@DESKTOP-NN7TD9I ~ $ "C:\Users\Me\AppData\Local\Programs\Zed\bin\zed.exe" --help The Zed CLI binary. This CLI is a separate binary that invokes Zed. ... They both launch Zed when double clicked, but only one works with CLI args. Fix is easy then, I just deleted "C:\Users\Me\AppData\Local\Programs\Zed" from my paths. I don't know if I added that or Zed added that path when installing (maybe from an earlier ver?), but there you have it.
  - miguelraz 6mo ago
    Glad to have "helped" here! :) Offer still stands if you run into other bugs that aren't in our issue tracker.

miguelraz 6mo ago

Zed support engineer here, that sounds like a bug! I have `zed --version` working on my Windows machine: PS C:\WINDOWS\system32> zed --version Zed 1.0.0 5ec84a926ef83865afb92d2a3d1ca3b419572cf9 – \\?\C:\Users\mrg\AppData\Local\Programs\Zed\Zed.exe If you're up for it, we can pair next week to get a proper bug report filed https://calendar.app.google/qPgW7q6upb3RqPjx5 https://calendar.app.google/qPgW7q6upb3RqPjx5

hdjrudni 6mo ago
I wasn't expecting that level of support, thanks for the offer! You said it should work, so I did some poking around. Uninstalled it, reinstalled it. Still didn't work. The "About" in app said I was running 1.0.0+stable Checked my environment paths and saw I had both C:\Users\Me\AppData\Local\Programs\Zed C:\Users\Me\AppData\Local\Programs\Zed\bin So I opened those paths in explorer, and there is indeed a zed.exe in both dirs. So I tried them explicitly: Me@DESKTOP-NN7TD9I ~ $ "C:\Users\Me\AppData\Local\Programs\Zed\Zed.exe" --help Me@DESKTOP-NN7TD9I ~ $ "C:\Users\Me\AppData\Local\Programs\Zed\bin\zed.exe" --help The Zed CLI binary. This CLI is a separate binary that invokes Zed. ... They both launch Zed when double clicked, but only one works with CLI args. Fix is easy then, I just deleted "C:\Users\Me\AppData\Local\Programs\Zed" from my paths. I don't know if I added that or Zed added that path when installing (maybe from an earlier ver?), but there you have it.
- miguelraz 6mo ago
  Glad to have "helped" here! :) Offer still stands if you run into other bugs that aren't in our issue tracker.