nucleo-matcher: Is there no way to turn off "match_paths" in the matcher config?

[markus-bauer]

See title.

There's set_match_paths, but it doesn't take a bool.

[evbo]

@markus-bauer it is a function that sets delimiter_chars to match filesystem paths (depending on os): https://docs.rs/nucleo-matcher/0.3.1/src/nucleo_matcher/config.rs.html#49

Could we make all fields public? For instance, only _ is a legal delimiter in my case but I have no way to set that:

pub struct Config {
    /// Characters that act as delimiters and provide bonus
    /// for matching the following char
    pub(crate) delimiter_chars: &'static [u8],
    /// Extra bonus for word boundary after whitespace character or beginning of the string
    pub(crate) bonus_boundary_white: u16,
    /// Extra bonus for word boundary after slash, colon, semi-colon, and comma
    pub(crate) bonus_boundary_delimiter: u16,
    pub(crate) initial_char_class: CharClass,

    /// Whether to normalize latin script characters to ASCII (enabled by default)
    pub normalize: bool,
    /// whether to ignore casing
    pub ignore_case: bool,
    /// Whether to provide a bonus to matches by their distance from the start
    /// of the haystack. The bonus is fairly small compared to the normal gap
    /// penalty to avoid messing with the normal score heuristic. This setting
    /// is not turned on by default and only recommended for autocompletion
    /// usecases where the expectation is that the user is typing the entire
    /// match. For a full fzf-like fuzzy matcher/picker word segmentation and
    /// explicit prefix literals should be used instead.
    pub prefer_prefix: bool,
}