greggyb

No worries on the delay. Thanks for an awesome service. I have emailed you separately. For anyone else following along, my IP geolocates to North Brunswick, NJ, USA (incorrect, but...

Perhaps there could be an allow_list for bash commands that can include regexes of allowed commands? For example, you could easily allow `^make \w+$`, and other similar known patterns for...

With more experimentation, it appears that this is specific to readline-enabled interpreters. Disabling readline with `$ dotnet fsi --readline-` seems to eliminate the error.

Ubuntu: ```shell $ dotnet --version 8.0.105 ``` FreeBSD: ```sh $ dotnet --version 8.0.100 ```

Extra context: Right now, due to a confluence of how FSAC and editors interact, working around this with the `--readline-` option has pretty negative knock-on effects for interactive programming with...

Sounding off here for a nonstandard environment. I develop F# on FreeBSD using Ionide-vim. There is a community port and package of dotnet to FreeBSD. `dotnet tool` works for me...

I'm seeing the same issue with Ionide-vim with the same option (`fsiExtraParameters`). This is particularly annoying, because `--readline-` is necessary when doing interactive development with scripts to work around [this...

I'm currently looking through the code and trying to figure out where a property that is named as if it is scoped to only the interpreter (`FSIExtraParameters`) ends up getting...

Some more digging and thinking. The option is a field on `FSharpConfig` and `FSharpConfigDto`. It is only ever set in two methods, both of which read from a Dto. One...

So I think that gets us to a design decision for implementing a fix here. I lean toward 1.2 1. Split the `FSIExtraParameters` into two fields: `FSIExtraInteractiveParameters` and `FSIExtraSharedParameters`. The...