Félix Saparelli comments

Results 581 comments of


                                            Félix Saparelli

[feature request] Run command on a specific event type.

Absolutely, do go on

[feature request] Run command on a specific event type.

This is now possible with the (experimental) tagged filterer mode: ``` $ env WATCHEXEC_FILTERER=tagged watchexec -f "kind=Create(*)" ... ``` Keeping this open until the feature makes it out of experimental...

Ignore apparently not working at all

This was probably fixed, or partially fixed, in 1.18.5, can you try that? Otherwise likely a duplicate of #241. I'll review that log tonight.

Ignore apparently not working at all

You can probably use `-i '**/_build/**'` instead to cover that for now.

Upon file change detection, watchexec is opening the file using the registered Windows handler for that file extension

Closing for lack of repro.

Upon file change detection, watchexec is opening the file using the registered Windows handler for that file extension

Hi @sergeevabc! Can you confirm (so we can finally start debugging this): - that you're seeing the same issue, and that's why you're commenting here? - that running the command...

Upon file change detection, watchexec is opening the file using the registered Windows handler for that file extension

the "copying changes" part is the "not simple" part, which we don't claim to be simple about (or anything about, really). It's not a common request! That said, you seem...

Upon file change detection, watchexec is opening the file using the registered Windows handler for that file extension

---- (unrelated to above convo with Aleksandr) ---- We've finally got some explanation for this bug! From twitter: > [this is] expected behavior, since PowerShell scripts are not interpreted by...

Upon file change detection, watchexec is opening the file using the registered Windows handler for that file extension

The solution seems to be to switch the default windows interpreter to PowerShell, and have a little detection going on to see if what's being executed is a `.bat` (plus...

Upon file change detection, watchexec is opening the file using the registered Windows handler for that file extension

There is now a new option, `--shell`, to select the shell to run the command, and `--shell=powershell` will effectively solve this issue. Idea is to switch the default to powershell...