LinusU / LinusU/rust-default-editor
Ability to spawn editor with arguments
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Thanks for this crate! Unfortunately I feel it is only getting me halfway where I want to be:
My `EDITOR` is set to `mvim -f`. The function returns me exactly that as well, but this is not something I can pass along to `std::process` before it is `sh-lexed`. But frankly, I'd rather not deal with this anyhow, I'd just love to call `default_editor::edit_file(&path)` and be done with.
Could you consider this as a feature request?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the crate's handling of the EDITOR value and the existing default_editor API, especially how the returned command is intended for std::process. Check the requested default_editor::edit_file(&path) entry point and determine how shell-lexed editor arguments should be passed. Done means callers can edit a path without handling sh-lexing themselves.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100