[1.0.2] Gif recording won't work on Arch Linux

[DistantThunder]

Describe the bug
Recording does not work

To Reproduce
Steps to reproduce the behavior:

1. Run menyoki record rec gif
2. See error

Expected behavior
The recording begins?

Screenshots/Logs

[2020-12-08T19:24:31 INFO menyoki::x11::window] Starting in 3[2020-12-08T19:24:31 INFO menyoki::util::command] Running the command...
thread 'main' panicked at 'Failed to run the command: Os { code: 2, kind: NotFound, message: "No such file or directory" }', src/app.rs:212:18
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fish : Tâche , 'LANG=C menyoki record rec gif' terminée par le signal SIGABRT (Abandon)

System Information

• OS: Arch Linux x86_64 5.9.9-arch1-1
• Rust Version: 1.48.0
• Project Version: 1.0.2

Additional context
N/A

[orhun]

1. Run `record rec gif` parameters

Try menyoki rec gif.

Edit: What are the exact parameters that you're using to run menyoki?

[DistantThunder]

Oh, I was misusing them, with the correct command it works. Sorry for the trouble.

I'm trying to use it together with slop so that I can use it in a CLI-less style, but I've to figure out how to start the recording after selection is done.

[orhun]

Oh, I was misusing them, with the correct command it works. Sorry for the trouble.

No worries 👍🏼

I'm trying to use it together with slop so that I can use it in a CLI-less style, but I've to figure out how to start the recording after selection is done.

menyoki record --root --size $(slop)

You have to press record key bindings after slop selection is done basically. I could've implement without it but it contradicts with my design choice.

Also about the Failed to run the command message, menyoki can run a command and record/capture it's output. So it probably thought one of your misused arguments was a command and tried to run it.

[DistantThunder]

You have to press record key bindings after slop selection is done basically. I could've implement without it but it contradicts with my design choice.

Alright thanks. I can't help but think it'd be nice to have a flag to start right away as it would allow powerful workflow by just mapping menyoki to a something like Ctrl-PrintScr, selecting the area you want to record and then you're done. But indeed without any kind of feedback, the user is a bit blind to what's happening behind the scene and this kind of workflow typically calls for some kind of visual feedback which may not be the project scope.

Thank you for taking your time to develop this and answer to annoying users!

[orhun]

Okay I changed the default behaviour a little bit:

menyoki cap --root --size $(slop)

And if you still want to confirm the selection with action keys (LAlt-S), use --select: