* `child_pty` => `pty.js`
* Create a frameless window on Windows and Linux
* Add a brand new UI for Linux and Windows 💅
* [Windows] Fix plugin installation
* [Windows] Fix the `build` script
* [Windows] Add a bigger `icon.ico`
* [Mac] Add `WebKitAppRegion: drag` when running on macOS
* Fix code style 🤔
* Add `appveyor.yml`
* Fix code style (again)
* [Windows] Fix AppVeyor's `install` script
* [Windows] Try a new AppVeyor config
* [Windows] Set the binary path so Spectron can run the tests
* [Windows] Try to build on x64
* Try again to build on x64
* Try one more time 😩
* Throw an error to indicate that `pty.js` was built incorrectly
* [Win/Linux] Add `display: hidden` to <Tabs /> if tabs.length === 1
* [Win/Linux] Reorganize SVGs – via @CodeTheory
* [Win/Linux] Fix the hamburger menu height
* Make the SVGs look better with `shape-rendering: crispEdges;`
* [Win/Linux] Add config options for the window controls and the 🍔 menu
* Add `electron-squirrel-startup` dependency
* [Win] Handle Squirrel commands
* [Win/Linux] Fix default color for the 🍔 and window controls – via @CodeTheory
* [Win/Linux] Add some padding - via @CodeTheory
* [Win/Linux] Add hover states – via @CodeTheory
* [Win] Fix empty window/tab titles
* [Win] Fix opening Preferences (#978)
* [Win] Fix opening Preferences
* Update ui.js
* Update ui.js
* Enhance messages and default editor
* [Win] Add dependency instructions to the README.md [skip ci]
* Fix code style
* [Win/Linux] Check the number of open windows before quitting the app
* increase timeout for update checks
It seems like, there are lots of them and GitHub is not happy.
So increasing timeout 6x should fix that. In the end there is no need
to check updates every 5 minutes.
Fix#880
* restore check updates on start
@Tyriar brought up a good point in #123 that the close menu items can be
ambiguous and misleading. This clarifies them so you know exactly what
you're closing.
Fixes#123.
* Comply with prefer-default-export rule for findBySession function
* Remove XO's prefer-default-export rule
* Comply with prefer-default-export rule for init function
* Comply with prefer-default-export rule for getRootGroups function
* Comply with prefer-default-export rule for INIT constant
* Comply with prefer-default-export rule for isExecutable function
* Fix default export for constants
* Comply with prefer-default-export rule for last function
* Comply with prefer-default-export rule for getColorList function
Default `err.message` notification is not helpful,
because it lacks stack and context.
it doesnt hurt for end users to add `console.error(err)`,
because they arent gonna see it. Though, as far as `console.error`
is being logged in Electron console, developers will get
enough information to identify problems with plugin they are developing.
fetchNotifications error can happen in two cases:
* https://hyper-news.now.sh is down
* you are offline
In both cases it doesn't hurt to wait half an hour.
PS. right now it hurts, when you are offline and developing
anything for Hyper, `console.error` logs the same error
every 10s and ruins your investigation.
* Create an issue template
* Make it clear what `Vanilla` is
* Create pull_request_template.md
* Update issue_template.md
* Update pull_request_template.md
* Add `https://`
* More information for maintainer contributions
* Be inclusive of other systems
* Add a random profileId to hterm instance to differentiate PreferenceManager used internally
* Use getPrefs() method instead of accessing prefs_ private property directly
* Add pseudo quick full screen
* Record window size before entering full screen
* Restore window size when leaving full screen
* Toggle menu items for quick full screen
* Remove redundant filters
* Add accelerators for Linux
* Only save window state when not full screen
* Run the one tests that exists in Travis before a release
* switched back to being a nodejs project
* cleaned up travis config
* removed xcode version since it is the default value
source: https://docs.travis-ci.com/user/osx-ci-environment/#OS-X-Version
* trying to get 2 builds (instead of 3) out of Travis
Most web clients apply a default white background to web pages, so some
websites omit explicitly setting their page backgrounds to white. The
default black background on the webview component was making some sites
unreadable. This commit just changes it from black to white.
