Zed CLI new window lauch changes

[Salman-Sali]

Body

What are you proposing?

zed <path> used to lauch a new window. Now its lauches on already open window. zed -n <path> is the new zed <path>.

Why does this matter?

Why change some thing like this. This is already a muscle memory across every app.

[JonGretar]

The first time you used the zed cli after update it asked you which behaviour to make default. But you can change it in settings.json.

  "cli_default_open_behavior": "new_window",

[franciskafyi]

@Salman-Sali does that solve this for you?

[Salman-Sali]

@Salman-Sali does that solve this for you?

Yes. Thank you @JonGretar

@franciskafyi
Don't you think default behaviour should be new_window?
I am not talking about me. I already solved it.
I am talking about new users. New window is already the default behaviour in vscode. I think coming from vscode people will expect that to be the default. Making transition better.

I didn't see the message Jon mentioned because I am using Button Rig to trigger the command to open my repo. If there is a message and its visible, then no problem I guess.

[franciskafyi]

We talked a lot about it internally, but with the introduction of Parallel Agents and the Sidebar we decided to change the default. We ended up including CLI "onboarding" + a setting to accommodate users who don't like the new behavior.

Happy to keep the discussion open but we're feeling bullish on this new workflow and do not plan to revert our decision.

[Salman-Sali]

No worries. I was just addressing my perspective. Now that I know yours, it makes sense. You can close the discussion if you want to.

[cpuccino]

This one got me too 😆