RoloEdits

Yeah, currently this pr touches `shellwords`. Which I don't think it should. Unless im missing something, this can be done with interpreting the args as the text input, `%{filename}`, and...

Ah, I see. With the changes I am making for the args I changed the `MappableCommand::Typeable.args` to a `String` ```rust pub enum MappableCommand { Typable { name: String, args: String,...

A working concept with what I posted: ```toml "A-," = [":sh echo `%{basename} %{filename} %{dirname} %{cwd} %{linenumber} %{selection}`"] ```  Unless there is some other reason for parsing the variables...

I'm not sure what changes will be proposed for my `Args` refactor pr, or if it might just be rejected altogether. For trying to coordinate multiple prs, I think we...

You mean for the `:echo` command introduced here? I believe this could be a static thing with the `CommandSigniture`.

Yeah, I believe you can provide a `Vec` , `vec!["%{filename}"]`, that gets resolved by the completer. When a space is the final part of an input, for example, it should...

And perhaps its actually **not** desired to parse in a way that respects whitespace? With the `Args` here being an iterator, you could filter all that aren't `}` and then...

@davidkna Want to get some feedback on the design of this before going forward, as you were the one who mentioned it before. Currently I just have it tied to...

So doing some more digging, the `pyenv.cfg` file is separate from `pyenv`. So now what I am doing is to make it a separate version getter (just like the `pyenv`...

For python to be set up to use this out of the box, it needs to be added to the `language-servers` list. https://github.com/helix-editor/helix/blob/41db5d735eae03be9a69b1136844dac642484ed8/languages.toml#L847-L857