vercel / vercel/hyper

Hyperterm should run as background process

Open
#2,398 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

🛠 Type: Feature Request
Dominant language
TypeScript
Stars
44.7k
Forks
3.6k
Avg merge
21m
Merged PRs (30d)
1

Description

Thanks to zeit and the hyper community for making a hackable shell terminal. I'm researching & putting together a plugin and .rc collection for hyper, zsh, vi, et all with the bells and whistles.

I get this popup error "Javascript error occurred in the main process" very often when modifying .hyper.js . Can you disable that alert please since it occurs so much and it's not even caused by any errors in hyper.js -- when you restart the app the config file works. Maybe its just this "auto-reload" feature is too aggressive and needs to delay a bit

Second, i've used the overlay and summon plugins, to be able to toggle my terminal with the tilde key. Most common terminals like Tilda and Guake have this feature by default, so its sensible for hyper to include that. Don't rely on third party plugins because these have a bunch of errors. The tilde key ends up not actually opening Hyper half the time because it's crashed. Or in nemo file man the nemo tilde takes precedence over the hyper-overlay.

Hyperterm should always be running from boot and toggle with a key like tilde. Adding it to startup applications isn't a good solution because that actually launches it, I dont want it to be launched. Also when its launched on "startup applications" in ubuntu 17 the font is tiny HDPI, then when you close/open hyper the font size is normal again. Lastly, I often Alt+F4 hyper by reflex to close it or need to close it when a command hangs. Then the plugins / shortcut key no longer work to reopen and restart it. I've had to create another, separate shortcut key for launching Hyper -- i'd prefer if I could use the same key to launch if not running, hide, and show.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source files, tests, or entry points are named. Start by separating the requested background-process, startup, toggle-key, close, and configuration-reload behaviors, then inspect the desktop process and shortcut lifecycle; done means the requested behavior is defined consistently across the described Ubuntu and terminal scenarios.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
desktop, operating-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.