Peter Tripp

I feel you. Formatting twice is a pretty ugly hack, but the lack of stable formatting means it can't be used to enforce a code style (pre-commit hook, CI check,...

btw, are you are aware of any other case where Format requires multiple passes or is otherwise unstable?

I think this may have been solved by: - #11519 @naim94a If you still experience this with a current build please comment and I'm happy to reopen.

I believe this is caused by: - https://github.com/zed-industries/zed/issues/12389 If you have an error in your settings.json we don't immediately revert to the default settings, we leave your last working settings...

I'm going to close this issue in favor of the more general: - https://github.com/zed-industries/zed/issues/12698 - https://github.com/zed-industries/zed/issues/4327 Please 👍 vote on those to increase visibility and subscribe to track their progress....

@michealp-coder Currently Zed only restores open files that are within an open workspace/project folder. I believe this is an enhancement which would address your request: - https://github.com/zed-industries/zed/issues/15098 Although your issue...

Closing in favor of: - https://github.com/zed-industries/zed/issues/15722 This issue is older, but that one has more upvotes. Please 👍 and subscribe there to track progress.

Yeah, compiling the stock hello world example throws this error on windows ``` C:\Users\peter\code\pd-hello>cargo +nightly playdate run error: The filename, directory name, or volume label syntax is incorrect. (os error...

Bump. This unnecessarily adds a 10 second delay to `cargo playdate run` which is pretty bad. Even worse, it prevents using IDE tools like rust-analyzer because it too has rebuild...

I was using cargo-playdate to build/run, is there documentation or an example of how to build without it?