-
Notifications
You must be signed in to change notification settings - Fork 26
Cargo install failed #38
Comments
that's weird, I think it was in a working state two weeks ago, now it's not gonna work for a while, I want it to be a satisfying experience before it can be installed again! |
I was confused, because I remember that I was able to get the binary, but now I can't. I wanted to check on the new little improvements. If your program is not in release stage (under v1.0.0), then I assume that it is not production ready. Hence, could be not a satisfying experience. But I think you should give the option to be able to get the binary. On GitHub, if you are creating a release, you can flag it as "pre-release" or something (I don't remember), to let everyone know that it can have some bugs or unpolished things. |
I worked in it today, it's pretty rough (files won't open for some reason) but it's on the bin branch if you want to take a look! Also cargo install wouldn't work because this is not really published to crates.io (since typst isn't either and I depend on it) |
I'll close this when I or someone else add a little install guide to the readme |
You mean like this: git clone -b bin https://github.com/astrale-sharp/typst-fmt.git
cd typst-fmt
cargo build
mkdir -p ~/.local/bin
cp -f target/debug/typst-fmt ~/.local/bin/ With a note that |
Or more simply like this :
;) if you're interested in writing yours up go ahead, I'll merge no problems! (otherwise I'll do it tomorrow!) |
Yay, binary is back on master branch! But why it suddenly called |
@astrale-sharp, check #50. |
Hi, I wanted to try the formatter but
cargo install typst-fmt
(cargo 1.70.0) return the following error which seems weird since the Cargo.toml file in the repo contains a bin section. So I'm a confused. Does anyone else encounter this issue ?The text was updated successfully, but these errors were encountered: