Support current path in Windows
Open
Nobody has claimed this yet.
windows
- Dominant language
- Rust
- Stars
- 7.5k
- Forks
- 353
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 15
Description
Teletypewriter should be able to retrieve current path on windows as well
#[cfg(not(target_os = "windows"))]
{
if let Ok(path) = teletypewriter::foreground_process_path(
*current_context.main_fd,
current_context.shell_pid,
) {
working_dir = Some(path.to_string_lossy().to_string());
}
}
#[cfg(target_os = "windows")]
{
// if let Ok(path) = teletypewriter::foreground_process_path() {
// working_dir =
// Some(path.to_string_lossy().to_string());
// }
working_dir = None;
}
}
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 in frontends/rioterm/src/context.rs around the platform-specific blocks at lines 630-648. Trace how the non-Windows branch retrieves the foreground process path, then investigate the Windows equivalent; done means Teletypewriter supplies the current path on Windows instead of leaving working_dir unset.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100