shellfn icon indicating copy to clipboard operation
shellfn copied to clipboard

Rust proc macro for easily and safely use shell scripts in rust

Results 11 shellfn issues
Sort by recently updated
recently updated
newest added

E.g. ```` #[shell requirements="xmlstarlet"] fn foo(...) { ... } ``` or maybe? ``` #[shell] fn foo(...) { shell::requires("xmlstarlet"); ... } ``` should check if `xmlstarlet` is present and if not,...

e.g. #[shell] fn foo() { use BAR; r#" echo $BAR"# }

Currently, there is `impl Display` requirement for all input parameters. It would be great to accept parameters like &Path, PathBuf, impl AsRef etc. Maybe a trait like `IntoDisplay` could be...

Now, if shell command panics, it is impossible to find out what happened

Add an attribute to return trimmed output. Maybe it should also be a more generic feature and any kind of 'post processing' should be allowed?

There should be an attribute that would allow to use [piped](https://doc.rust-lang.org/std/process/struct.Stdio.html#method.piped) stdout and stderr

I have an executable that uses shellfn::shell to execute a command and the executable has the SUID bit set, but the euid does not get preserved in the shell, whereas...

Currently I see no way to pass in an OsStr as an argument to a shell function. The big benefit I see to the current way is that it allows...

`Rust proc macro for easily and safely use shell scripts in rust` should become something like `Procedural macro for easily and safely using shell scripts in Rust`

I'm trying to include file using include_str! macro: `#[shell(cmd = "python -c")] fn run_python(name: &str) -> Result { include_str("main.py") } ` but getting an error on compilation: ` --> src/main.rs:3:1...