Denys Séguret comments

Results 761 comments of


                                            Denys Séguret

:write_stdout and :writeln_stdout internals

An approach might be to allow more settings to be carried by verb arguments, using the syntax I introduced at https://github.com/Canop/broot/blob/main/CHANGELOG.md#v091---2019-07-29 This could for example be `write_stdout {file:comma-separated};:quit` or `write_stdout...

:write_stdout and :writeln_stdout internals

I'm dropping this PR and will try another approach.

Output from Br shell function in powershell doesn't print to stdout

I clearly prefer the correct script to be installed by broot. But as I can't test myself on Windows, I let you create and check the PR.

Output from Br shell function in powershell doesn't print to stdout

Instead of changing `:print_path`, which is too specific anyway, why not having a `:write_stdout` verb, similar to the current `:write_output` but writing to stdout instead of writing to the file...

Output from Br shell function in powershell doesn't print to stdout

@AeliusSaionji Can you have a look at https://github.com/Canop/broot/pull/901 ?

Output from Br shell function in powershell doesn't print to stdout

@Alfamari This is very relevant and something I didn't think about

Output from Br shell function in powershell doesn't print to stdout

As you probably know, I don't test on Windows and I need Windows users to test, analyze, and clarify the situation on Windows. It's also hard for me to follow...

bacon doesn't react to change in build.rs in workspace member

I don't reproduce that. Can you please post an example I can reproduce ?

bacon doesn't react to change in build.rs in workspace member

no reproduction

[Feature] post process application output

What you want is * having bacon display the warning and errors in your program if any * and if none, have it display the output of the running program,...