* `command` => `mod`
* `Option` => `Alt`
* Allow hterm to consume a keyboard event only if it's not a Hyper accelerator
* Remove `console.log`s
* Say no to bikeshedding
* We already clear the selection on `onKeyDown`
* Add comments
* Remove meaningless comment
* Add fullscreen shortcut for Windows and Linux
* Use the accelerators defined in `accelerators.js` for the app menu
* feat(session): add session_active class to panels
* fix(active-session): rename active session class
see #905
* fix(active-session): rename prop name to `isTermActive`
* Added pressed state to window buttons on windows / linux
* Removed transition causing flicker
* Do not reset color on close button while not hovering but active
* Add container with a fixed width around unicode characters
* Make container width dynamic and fix wide chars clipping issue
* Finer control on the creation of containers for text inserted in the terminal
* ime
* Fix code style
* Add visual feedback for composition events
* Temporarily disable `hterm`'s `onKeyDown` hacks
* Replicate the focus/blur state of our caret on the `hterm` caret
* Fix: focus our caret when there's a tab change
* `caret_` => `hyperCaret`
* Reorg: move the caret hacks to the `hterm.js` extensions
* Remove `console.log`
* Remove the `Dead key` hack and reenable keyboard commands
* Add a (temporary?) fix to re-enable text selection
* Check for a selection `onMouseUp` instead `onFocus`
* Fix wrong buggy hterm's cursor styling on term focus/blur
* Fix the cursor style after the bell rings – closes#674
* Enable `acceptFirstMouse` to focus the correct term – closes#861
* Fix code style
* Fix: clear the `hyper-caret` when a char is inserted via the IME dialog
* Remove useless function
* Add coments regarding text selection
* Fix code style
* Upgrade `electron-builder` to its latest version and pin it
* Fix linux executable path – see electron-userland/electron-builder#877
* [Windows] Build `squirrel` executable instead of `nsis`
* `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.
