Mark Tyrkba

### I've followed nobuild guide but anyway keep facing this error: ``` error: linking with `cc` failed: exit status: 1 | = note: LC_ALL="C" PATH="/home/yarson/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/bin:/home/yarson/.cargo/bin:/usr/condabin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/opt/rocm/bin:/usr/lib/rustup/bin" VSLANG="1033" "cc" "-m64" "/tmp/rustcv68FIE/symbols.o" "/home/yarson/Coding/probe/raylib_rust/target/release/deps/raylib_rust-4d232eb3bbaff2ef.raylib_rust.311e897e0720339c-cgu.0.rcgu.o"...

I've been using `nakst/gf` for quite some time already, and I've noticed, that having the `args_from_cmd` and `executable_path_from_cmd` keys would be pretty convenient. Whenever I open `gf` I constantly have...

With `env-libvpx-sys` version being set to `5.1.0` or `5`, on my machine the `record-screen` example fails to build with this error: ``` --- stderr thread 'main' panicked at /home/rakivo/.cargo/registry/src/index.crates.io-6f17d22bba15001f/bindgen-0.55.1/src/ir/context.rs:838:9: "vpx_codec_ctx_union_(unnamed_at_/usr/include/vpx/_/vpx_codec_h_206_3)"...

I’ve been using Snitch for the past few months, and the tool is really great. However, I always wanted to include the TODO’s title in the commit messages to make...