How to make generated app to use current working dir as its working dir instead of app's dir?
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.6k
- Forks
- 174
- PR merge metrics
- No merged PRs in 30d
Description
I generated an app called mysigner at $HOME/bin/signer/mysigner using packr. It is fast when I launched it.
mysigner takes file/folders as parameters. When I launch mysigner from $HOME/work dir, all the relative file paths are getting resolved to $HOME/bin/signer dir. That doesn't make sense.
What is the trick to make it respect the current working dir and not change to mysigner app location?
Thanks
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 tracing how packr builds and launches the generated app, focusing on how the JVM process receives or changes its working directory. Reproduce the relative-path behavior from a different directory, then verify that the generated application preserves the caller's current working directory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100