You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: config at ~/.hyper.js still supported, but will be ignored, if config in application directory present. Otherwise it will be moved to the application directory at first run.
Observations:
On a fresh install of Hyper on macOS 10.15:
~/.hyper.js is created
~/Library/Application Support/Hyper/.hyper.js is not created
Changes saved to ~/.hyper.js are reflected in the app
If I copy and paste customized config contents into ~/Library/Application Support/Hyper/.hyper.js and then delete ~/.hyper.js, Hyper does not seem to recognize the customized config.
It seems that the documentation does not represent the current behavior of Hyper.
I have only recently begun to explore Hyper, so I would like to understand this better: is the documentation outdated or is it new information that is planned for a future release, but is not yet relevant?
Either way, the docs should probably be updated to reflect the current app behavior.
The text was updated successfully, but these errors were encountered:
At https://hyper.is/#config-location, it reads:
Observations:
On a fresh install of Hyper on macOS 10.15:
~/.hyper.js
is created~/Library/Application Support/Hyper/.hyper.js
is not createdChanges saved to
~/.hyper.js
are reflected in the appIf I copy and paste customized config contents into
~/Library/Application Support/Hyper/.hyper.js
and then delete~/.hyper.js
, Hyper does not seem to recognize the customized config.It seems that the documentation does not represent the current behavior of Hyper.
I have only recently begun to explore Hyper, so I would like to understand this better: is the documentation outdated or is it new information that is planned for a future release, but is not yet relevant?
Either way, the docs should probably be updated to reflect the current app behavior.
The text was updated successfully, but these errors were encountered: