Summary: This diff contains a few major changes: 1. Scribe is no longer used for the text editor. It's just a plain contenteditable region. The toolbar items (bold, italic, underline) still work. Scribe was causing React inconcistency issues in the following scenario: - View thread with draft, edit draft - Move to another thread - Move back to thread with draft - Move to another thread. Notice that one or more messages from thread with draft are still there. There may be a way to fix this, but I tried for hours and there are Github Issues open on it's repository asking for React compatibility, so it may be fixed soon. For now contenteditable is working great. 2. Action.saveDraft() is no longer debounced in the DraftStore. Instead, firing that action causes the save to happen immediately, and the DraftStoreProxy has a new "DraftChangeSet" class which is responsbile for batching saves as the user interacts with the ComposerView. There are a couple big wins here: - In the future, we may want to be able to call Action.saveDraft() in other situations and it should behave like a normal action. We may also want to expose the DraftStoreProxy as an easy way of backing interactive draft UI. - Previously, when you added a contact to To/CC/BCC, this happened: <input> -> Action.saveDraft -> (delay!!) -> Database -> DraftStore -> DraftStoreProxy -> View Updates Increasing the delay to something reasonable like 200msec meant there was 200msec of lag before you saw the new view state. To fix this, I created a new class called DraftChangeSet which is responsible for accumulating changes as they're made and firing Action.saveDraft. "Adding" a change to the change set also causes the Draft provided by the DraftStoreProxy to change immediately (the changes are a temporary layer on top of the database object). This means no delay while changes are being applied. There's a better explanation in the source! This diff includes a few minor fixes as well: 1. Draft.state is gone—use Message.object = draft instead 2. String model attributes should never be null 3. Pre-send checks that can cancel draft send 4. Put the entire curl history and task queue into feedback reports 5. Cache localIds for extra speed 6. Move us up to latest React Test Plan: No new tests - once we lock down this new design I'll write tests for the DraftChangeSet Reviewers: evan Reviewed By: evan Differential Revision: https://review.inboxapp.com/D1125
7 KiB
Customizing Atom
To change a setting, configure a theme, or install a package just open the
Settings view in the current window by pressing cmd-,
.
Changing The Theme
Atom comes with both light and dark UI themes as well as several syntax themes. You are also encouraged to create or fork your own theme.
To change the active theme just open the Settings view (cmd-,
) and select the
Themes
section from the left hand side. You will see a drop-down menu to
change the active Syntax and UI themes.
You can also install more themes from here by browsing the featured themes or searching for a specific theme.
Installing Packages
You can install non-bundled packages by going to the Packages
section on left
hand side of the Settings view (cmd-,
). You will see several featured packages
and you can also search for packages from here. The packages listed here have
been published to atom.io which is the official
registry for Atom packages.
You can also install packages from the command line using apm
.
Check that you have apm
installed by running the following command in your
terminal:
apm help install
You should see a message print out with details about the apm install
command.
If you do not, launch Atom and run the Atom > Install Shell Commands menu
to install the apm
and atom
commands.
You can also install packages by using the apm install
command:
-
apm install <package_name>
to install the latest version. -
apm install <package_name>@<package_version>
to install a specific version.
For example apm install emmet@0.1.5
installs the 0.1.5
release of the
Emmet package into ~/.atom/packages
.
You can also use apm
to find new packages to install:
-
apm search coffee
to search for CoffeeScript packages. -
apm view emmet
to see more information about a specific package.
Customizing Key Bindings
Atom keymaps work similarly to style sheets. Just as style sheets use selectors to apply styles to elements, Atom keymaps use selectors to associate keystrokes with events in specific contexts. Here's a small example, excerpted from Atom's built-in keymaps:
'atom-text-editor':
'enter': 'editor:newline'
'atom-text-editor[mini] input':
'enter': 'core:confirm'
This keymap defines the meaning of enter
in two different contexts. In a
normal editor, pressing enter
emits the editor:newline
event, which causes
the editor to insert a newline. But if the same keystroke occurs inside of a
select list's mini-editor, it instead emits the core:confirm
event based on
the binding in the more-specific selector.
By default, ~/.atom/keymap.cson
is loaded when Atom is started. It will always
be loaded last, giving you the chance to override bindings that are defined by
Atom's core keymaps or third-party packages.
You can open this file in an editor from the Atom > Open Your Keymap menu.
You'll want to know all the commands available to you. Open the Settings panel
(cmd-,
) and select the Keybindings tab. It will show you all the keybindings
currently in use.
Advanced Configuration
Atom loads configuration settings from the config.cson
file in your ~/.atom
directory, which contains CoffeeScript-style JSON (CSON):
'core':
'excludeVcsIgnoredPaths': true
'editor':
'fontSize': 18
The configuration itself is grouped by the package name or one of the two core
namespaces: core
and editor
.
You can open this file in an editor from the Atom > Open Your Config menu.
Configuration Key Reference
core
disabledPackages
: An array of package names to disableexcludeVcsIgnoredPaths
: Don't search within files specified by .gitignorefollowSymlinks
: Follow symlinks when searching and scanning root directoryignoredNames
: File names to ignore across all of AtomprojectHome
: The directory where projects are assumed to be locatedthemes
: An array of theme names to load, in cascading order
editor
autoIndent
: Enable/disable basic auto-indent (defaults totrue
)nonWordCharacters
: A string of non-word characters to define word boundariesfontSize
: The editor font sizefontFamily
: The editor font familyinvisibles
: Specify characters that Atom renders for invisibles in this hashtab
: Hard tab characterscr
: Carriage return (for Microsoft-style line endings)eol
:\n
charactersspace
: Leading and trailing space characters
preferredLineLength
: Identifies the length of a line (defaults to80
)showInvisibles
: Whether to render placeholders for invisible characters (defaults tofalse
)showIndentGuide
: Show/hide indent indicators within the editorshowLineNumbers
: Show/hide line numbers within the guttersoftWrap
: Enable/disable soft wrapping of text within the editorsoftWrapAtPreferredLineLength
: Enable/disable soft line wrapping atpreferredLineLength
tabLength
: Number of spaces within a tab (defaults to2
)
fuzzyFinder
ignoredNames
: Files to ignore only in the fuzzy-finder
whitespace
ensureSingleTrailingNewline
: Whether to reduce multiple newlines to one at the end of filesremoveTrailingWhitespace
: Enable/disable striping of whitespace at the end of lines (defaults totrue
)
wrap-guide
columns
: Array of hashes with apattern
andcolumn
key to match the the path of the current editor to a column position.
Quick Personal Hacks
init.coffee
When Atom finishes loading, it will evaluate init.coffee in your ~/.atom directory, giving you a chance to run arbitrary personal CoffeeScript code to make customizations. You have full access to Atom's API from code in this file. If customizations become extensive, consider creating a package.
You can open this file in an editor from the Atom > Open Your Init Script menu.
For example, if you have the Audio Beep configuration setting enabled, you could add the following code to your ~/.atom/init.coffee file to have Atom greet you with an audio beep every time it loads:
atom.beep()
This file can also be named init.js and contain JavaScript code.
styles.less
If you want to apply quick-and-dirty personal styling changes without creating an entire theme that you intend to publish, you can add styles to the styles.less file in your ~/.atom directory.
You can open this file in an editor from the Atom > Open Your Stylesheet menu.
For example, to change the color of the cursor, you could add the following rule to your ~/.atom/styles.less file:
atom-text-editor::shadow .cursor {
border-color: pink;
}
Unfamiliar with Less? Read more about it here.
This file can also be named styles.css and contain CSS.