extrawurst
extrawurst
so its basically about adding a configuration of what program is spawned when triggering an `edit`?
@alerque please add a changelog entry matching other contributions
thanks for your contribution. note that i will change the env name to `BUILD_GIT_COMMIT_ID`. hope that is ok
i am currently not maintaining the winget deploys at all myself. would be awesome to integrate that into our CD pipeline. care to open a PR?
its interesting. my first thought: impossible we build with our MSRV on CI, only to find out no, I forgot to update that. problem found? wrong, the update shows that...
damn maybe its just the same as #2090 - can you try building with `cargo build --release --locked` or `cargo install --path "." --locked` ?
Right now you can only view a single files history
But the procedure should be easy to extend for paths
> until ron gets intellisence support like JSON/YAML where user can create any arbitrary schemas and associate them with any files. I am all for that 👌 Working on this...
see #2079 - we first have to wait for a new ratatui release with a fix for https://github.com/ratatui-org/ratatui/issues/961#issuecomment-1954699037