microsoft / microsoft/terminal
Investigate and ensure `wt.exe` is always `argv[0]`
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 105k
- Forks
- 9.6k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 29
Description
I have seen Windows executables receive arguments BOTH ways. I don't know what the circumstance is offhand that makes it happen one way or the other. You will want to deal with both the presence and absence of your own executable name at argv[0].
Originally posted by @miniksa in https://github.com/microsoft/terminal/pull/4023
If it's not, then we'll need to mitigate this somehow, since we're leaning on that pretty hard at the moment
Contributor guide
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 locating the Windows Terminal wt.exe entry point and how command-line arguments are constructed on Windows. Reproduce cases where the executable name is present or absent from argv[0], then verify that both forms are handled so downstream argument processing consistently sees wt.exe there.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100