Path ignored when an argument is specified
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 44.7k
- Forks
- 3.6k
- Avg merge
- 21m
- Merged PRs (30d)
- 1
Description
- I am on the latest Hyper.app version
- I have searched the issues of this repo and believe that this is not a duplicate
- OS version and name: Arch Linux
- Hyper.app version: 2.0.0-canary.14
- Link of a Gist with the contents of your .hyper.js: https://gist.github.com/Mrtenz/688bbfb6b4b6ca40a0232ea32967b560
- Relevant information from devtools (CMD+ALT+I on macOS, CTRL+SHIFT+I elsewhere):
- The issue is reproducible in vanilla Hyper.app: Yes
Issue
I am trying to make Hyper launch from Nautilus using the context menu. Because the terminals that can be used are hardcoded, I created a symlink from /usr/bin/hyper to /usr/bin/gnome-terminal. Now, when I launch the terminal using the context menu it does open Hyper, but not on the current path I was on with Nautilus.
I figured that Nautilus uses gnome-terminal -e [path] to launch the terminal, and as far as I know there is no way to change what arguments are used. The issue is that when any argument is passed to hyper, such as hyper -e ~/Documents, Hyper will ignore the path and open the home folder. It would be nice if Hyper could open the path even though an invalid argument is set.
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 reproducing the reported launch from Nautilus with hyper -e ~/Documents and compare it with a launch that has no argument. Trace Hyper's command-line argument handling to determine why the supplied path is ignored; done means the path is preserved even when an invalid argument is present, including in vanilla Hyper.app.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli, desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100