From 988bd1e4c6ce438dabd244b9de2e5af0fd92f799 Mon Sep 17 00:00:00 2001 From: Ronald Eddy Jr Date: Mon, 25 Dec 2017 23:14:18 -0800 Subject: [PATCH] Update: HTTP -> HTTPS URLs updated to use HTTPS protocol where appropriate to improve security and privacy. --- README.md | 2 +- content/behind-atom/sections/keymaps-in-depth.md | 2 +- .../contributing-to-official-atom-packages.md | 2 +- .../sections/converting-from-textmate.md | 4 ++-- content/hacking-atom/sections/creating-a-grammar.md | 8 ++++---- .../hacking-atom/sections/hacking-on-atom-core.md | 2 +- content/hacking-atom/sections/iconography.md | 2 +- content/hacking-atom/sections/package-word-count.md | 4 ++-- content/hacking-atom/sections/publishing.md | 4 ++-- content/hacking-atom/sections/writing-specs.md | 8 ++++---- .../sections/removing-shadow-dom-styles.md | 2 +- .../sections/upgrading-your-package.md | 2 +- .../sections/upgrading-your-syntax-theme.md | 4 ++-- .../upgrading-your-ui-theme-or-package-selectors.md | 4 ++-- content/using-atom/sections/atom-packages.md | 2 +- content/using-atom/sections/basic-customization.md | 2 +- content/using-atom/sections/find-and-replace.md | 2 +- content/using-atom/sections/moving-in-atom.md | 2 +- .../using-atom/sections/version-control-in-atom.md | 2 +- layouts/includes/bottom_bar.html | 2 +- layouts/includes/favicon.html | 2 +- layouts/includes/top_bar.html | 2 +- layouts/toc.html | 2 +- outline.md | 12 ++++++------ 24 files changed, 40 insertions(+), 40 deletions(-) diff --git a/README.md b/README.md index ab316606ec..00a1c7026a 100644 --- a/README.md +++ b/README.md @@ -2,7 +2,7 @@ This is the Atom book. Everything you need to know in order to use and hack Atom is in this Flight Manual. -You can find this book online at: http://flight-manual.atom.io +You can find this book online at: https://flight-manual.atom.io This book is open source under a Creative Commons license. diff --git a/content/behind-atom/sections/keymaps-in-depth.md b/content/behind-atom/sections/keymaps-in-depth.md index 1d83d43c29..90a909aa7c 100644 --- a/content/behind-atom/sections/keymaps-in-depth.md +++ b/content/behind-atom/sections/keymaps-in-depth.md @@ -211,7 +211,7 @@ When the event handler observes that the cursor does not follow a valid prefix, #### Overriding Atom's Keyboard Layout Recognition -Sometimes the problem isn't mapping the command to a key combination, the problem is that Atom doesn't recognize properly what keys you're pressing. This is due to [some limitations in how Chromium reports keyboard events](http://blog.atom.io/2016/10/17/the-wonderful-world-of-keyboards.html). But even this can be customized now. +Sometimes the problem isn't mapping the command to a key combination, the problem is that Atom doesn't recognize properly what keys you're pressing. This is due to [some limitations in how Chromium reports keyboard events](https://blog.atom.io/2016/10/17/the-wonderful-world-of-keyboards.html). But even this can be customized now. You can add the following to your `init.coffee` to send Ctrl+@ when you press Ctrl+Alt+G: diff --git a/content/hacking-atom/sections/contributing-to-official-atom-packages.md b/content/hacking-atom/sections/contributing-to-official-atom-packages.md index a77bfab6f1..8e598e692a 100644 --- a/content/hacking-atom/sections/contributing-to-official-atom-packages.md +++ b/content/hacking-atom/sections/contributing-to-official-atom-packages.md @@ -9,7 +9,7 @@ If you think you know which package is causing the issue you are reporting, feel ##### Cloning -The first step is creating your own clone. For some packages, you may also need to install the [requirements necessary for building Atom](http://flight-manual.atom.io/hacking-atom/sections/hacking-on-atom-core/#building) in order to run `apm install`. +The first step is creating your own clone. For some packages, you may also need to install the [requirements necessary for building Atom](https://flight-manual.atom.io/hacking-atom/sections/hacking-on-atom-core/#building) in order to run `apm install`. For example, if you want to make changes to the `tree-view` package, fork the repo on your github account, then clone it: diff --git a/content/hacking-atom/sections/converting-from-textmate.md b/content/hacking-atom/sections/converting-from-textmate.md index 32457b6217..c66c92daa0 100644 --- a/content/hacking-atom/sections/converting-from-textmate.md +++ b/content/hacking-atom/sections/converting-from-textmate.md @@ -3,7 +3,7 @@ title: Converting from TextMate --- ### Converting from TextMate -It's possible that you have themes or grammars from [TextMate](http://macromates.com) that you like and use and would like to convert to Atom. If so, you're in luck because there are tools to help with the conversion. +It's possible that you have themes or grammars from [TextMate](https://macromates.com) that you like and use and would like to convert to Atom. If so, you're in luck because there are tools to help with the conversion. #### Converting a TextMate Grammar Bundle @@ -21,7 +21,7 @@ You can now change directory into `language-r` to see the converted bundle. Once #### Converting a TextMate Syntax Theme -This section will go over how to convert a [TextMate](http://macromates.com) theme to an Atom +This section will go over how to convert a [TextMate](https://macromates.com) theme to an Atom theme. ##### Differences diff --git a/content/hacking-atom/sections/creating-a-grammar.md b/content/hacking-atom/sections/creating-a-grammar.md index 1d35c5ae03..71cf1ba272 100644 --- a/content/hacking-atom/sections/creating-a-grammar.md +++ b/content/hacking-atom/sections/creating-a-grammar.md @@ -15,11 +15,11 @@ Grammars power Atom's syntax highlighting. Each grammar provides a set of _regex Grammars depend heavily on regexes, and you should be comfortable with interpreting and writing regexes before continuing. Note that Atom uses the Oniguruma engine, which is very similar to the PCRE or Perl regex engines. Here are some resources to help you out: -* http://www.regular-expressions.info/tutorial.html provides a comprehensive regex tutorial -* http://www.rexegg.com/regex-quickstart.html contains a cheat sheet for various regex expressions +* https://www.regular-expressions.info/tutorial.html provides a comprehensive regex tutorial +* https://www.rexegg.com/regex-quickstart.html contains a cheat sheet for various regex expressions * https://regex101.com/ or https://regexr.com/ allows live prototyping -Grammar files are written in the [CSON](https://github.com/bevry/cson#what-is-cson) or [JSON](http://www.json.org/) format. Whichever one you decide to use is up to you, but this tutorial will be written in CSON. +Grammar files are written in the [CSON](https://github.com/bevry/cson#what-is-cson) or [JSON](https://www.json.org/) format. Whichever one you decide to use is up to you, but this tutorial will be written in CSON. #### Create the Package @@ -53,7 +53,7 @@ To start, let's add a basic pattern to tokenize the words `Flight Manual` whenev ] ``` -`match` is where your regex is contained, and `name` is the scope name that is to be applied to the entirety of the match. More information about scope names can be found in [Section 12.4 of the TextMate Manual](http://manual.macromates.com/en/language_grammars). +`match` is where your regex is contained, and `name` is the scope name that is to be applied to the entirety of the match. More information about scope names can be found in [Section 12.4 of the TextMate Manual](https://manual.macromates.com/en/language_grammars). {{#tip}} diff --git a/content/hacking-atom/sections/hacking-on-atom-core.md b/content/hacking-atom/sections/hacking-on-atom-core.md index 9825059df0..cb709ac60b 100644 --- a/content/hacking-atom/sections/hacking-on-atom-core.md +++ b/content/hacking-atom/sections/hacking-on-atom-core.md @@ -68,7 +68,7 @@ In order to build Atom from source, you need to have a number of other requireme * The `python.exe` must be available at `%SystemDrive%\Python27\python.exe`. If it is installed elsewhere create a symbolic link to the directory containing the `python.exe` using: `mklink /d %SystemDrive%\Python27 D:\elsewhere\Python27` * 7zip (7z.exe available from the command line) - for creating distribution zip files * Visual Studio, either: - * [Visual C++ Build Tools 2015](http://landinghub.visualstudio.com/visual-cpp-build-tools) + * [Visual C++ Build Tools 2015](https://landinghub.visualstudio.com/visual-cpp-build-tools) * [Visual Studio 2013 Update 5](https://www.visualstudio.com/en-us/downloads/download-visual-studio-vs) (Express Edition or better) * [Visual Studio 2015](https://www.visualstudio.com/en-us/downloads/download-visual-studio-vs) (Community Edition or better) diff --git a/content/hacking-atom/sections/iconography.md b/content/hacking-atom/sections/iconography.md index 0c624e5cbc..fefac6a110 100644 --- a/content/hacking-atom/sections/iconography.md +++ b/content/hacking-atom/sections/iconography.md @@ -9,7 +9,7 @@ Atom comes bundled with the [Octicons 4.4.0](https://github.com/github/octicons/ #### Overview -In the [Styleguide](http://flight-manual.atom.io/hacking-atom/sections/creating-a-theme/#atom-styleguide) under the "Icons" section you'll find all the Octicons that are available. +In the [Styleguide](https://flight-manual.atom.io/hacking-atom/sections/creating-a-theme/#atom-styleguide) under the "Icons" section you'll find all the Octicons that are available. ![Octicons in the Styleguide](../../images/iconography.png "Octicons in the Styleguide") diff --git a/content/hacking-atom/sections/package-word-count.md b/content/hacking-atom/sections/package-word-count.md index 8e247775af..2bb19d6ddf 100644 --- a/content/hacking-atom/sections/package-word-count.md +++ b/content/hacking-atom/sections/package-word-count.md @@ -40,7 +40,7 @@ Not every package will have (or need) all of these directories and the package g ##### `package.json` -Similar to [Node modules](http://en.wikipedia.org/wiki/Npm_(software)), Atom packages contain a `package.json` file in their top-level directory. This file contains metadata about the package, such as the path to its "main" module, library dependencies, and manifests specifying the order in which its resources should be loaded. +Similar to [Node modules](https://en.wikipedia.org/wiki/Npm_(software)), Atom packages contain a `package.json` file in their top-level directory. This file contains metadata about the package, such as the path to its "main" module, library dependencies, and manifests specifying the order in which its resources should be loaded. In addition to some of the regular [Node `package.json` keys](https://docs.npmjs.com/files/package.json) available, Atom `package.json` files have their own additions. @@ -110,7 +110,7 @@ Your package's top-level module is a singleton object that manages the lifecycle Your package's top-level module can implement the following basic methods: * `activate(state)`: This **optional** method is called when your package is activated. It is passed the state data from the last time the window was serialized if your module implements the `serialize()` method. Use this to do initialization work when your package is started (like setting up DOM elements or binding events). -* `initialize(state)`: (Available in Atom 1.14 and above) This **optional** method is similar to `activate()` but is called earlier. Whereas activation occurs after the workspace has been deserialized (and can therefore happen after [your package's deserializers](http://flight-manual.atom.io/behind-atom/sections/serialization-in-atom/#serialization-methods) have been called), `initialize()` is guaranteed to be called before everything. Use `activate()` if you want to be sure that the workspace is ready; use `initialize()` if you need to do some setup prior to your deserializers or view providers being invoked. +* `initialize(state)`: (Available in Atom 1.14 and above) This **optional** method is similar to `activate()` but is called earlier. Whereas activation occurs after the workspace has been deserialized (and can therefore happen after [your package's deserializers](https://flight-manual.atom.io/behind-atom/sections/serialization-in-atom/#serialization-methods) have been called), `initialize()` is guaranteed to be called before everything. Use `activate()` if you want to be sure that the workspace is ready; use `initialize()` if you need to do some setup prior to your deserializers or view providers being invoked. * `serialize()`: This **optional** method is called when the window is shutting down, allowing you to return JSON to represent the state of your component. When the window is later restored, the data you returned is passed to your module's `activate` method so you can restore your view to where the user left off. * `deactivate()`: This **optional** method is called when the window is shutting down. If your package is watching any files or holding external resources in any other way, release them here. If you're just subscribing to things on window, you don't need to worry because that's getting torn down anyway. diff --git a/content/hacking-atom/sections/publishing.md b/content/hacking-atom/sections/publishing.md index 68cc17348d..8dabf78101 100644 --- a/content/hacking-atom/sections/publishing.md +++ b/content/hacking-atom/sections/publishing.md @@ -25,7 +25,7 @@ Now let's review what the `apm publish` command does: 1. Registers the package name on atom.io if it is being published for the first time. 2. Updates the `version` field in the `package.json` file and commits it. -3. Creates a new [Git tag](http://git-scm.com/book/en/Git-Basics-Tagging) for the version being published. +3. Creates a new [Git tag](https://git-scm.com/book/en/Git-Basics-Tagging) for the version being published. 4. Pushes the tag and current branch up to GitHub. 5. Updates atom.io with the new version being published. @@ -54,6 +54,6 @@ The `minor` option to the publish command tells apm to increment the second numb The `patch` option to the publish command tells apm to increment the third number of the version before publishing so the published version will be `0.0.1` and the Git tag created will be `v0.0.1`. -Use `major` when you make a change that breaks backwards compatibility, like changing defaults or removing features. Use `minor` when adding new functionality or options, but without breaking backwards compatibility. Use `patch` when you've changed the implementation of existing features, but without changing the behaviour or options of your package. Check out [semantic versioning](http://semver.org) to learn more about best practices for versioning your package releases. +Use `major` when you make a change that breaks backwards compatibility, like changing defaults or removing features. Use `minor` when adding new functionality or options, but without breaking backwards compatibility. Use `patch` when you've changed the implementation of existing features, but without changing the behaviour or options of your package. Check out [semantic versioning](https://semver.org) to learn more about best practices for versioning your package releases. You can also run `apm help publish` to see all the available options and `apm help` to see all the other available commands. diff --git a/content/hacking-atom/sections/writing-specs.md b/content/hacking-atom/sections/writing-specs.md index a371bb2539..01d864ebb6 100644 --- a/content/hacking-atom/sections/writing-specs.md +++ b/content/hacking-atom/sections/writing-specs.md @@ -5,7 +5,7 @@ title: Writing specs We've looked at and written a few specs through the examples already. Now it's time to take a closer look at the spec framework itself. How exactly do you write tests in Atom? -Atom uses [Jasmine](http://jasmine.github.io/1.3/introduction.html) as its spec framework. Any new functionality should have specs to guard against regressions. +Atom uses [Jasmine](https://jasmine.github.io/1.3/introduction.html) as its spec framework. Any new functionality should have specs to guard against regressions. #### Create a New Spec @@ -43,7 +43,7 @@ describe "when a test is written", -> ##### Add One or More Expectations -The best way to learn about expectations is to read the [Jasmine documentation](http://jasmine.github.io/1.3/introduction.html#section-Expectations) about them. Below is a simple example. +The best way to learn about expectations is to read the [Jasmine documentation](https://jasmine.github.io/1.3/introduction.html#section-Expectations) about them. Below is a simple example. ```coffee describe "when a test is written", -> @@ -146,7 +146,7 @@ describe "fs.readdir(path, cb)", -> expect(spy).toHaveBeenCalledWith(null, ['example.coffee']) ``` -For a more detailed documentation on asynchronous tests please visit the [Jasmine documentation](http://jasmine.github.io/1.3/introduction.html#section-Asynchronous_Support). +For a more detailed documentation on asynchronous tests please visit the [Jasmine documentation](https://jasmine.github.io/1.3/introduction.html#section-Asynchronous_Support). #### Running Specs @@ -163,7 +163,7 @@ describe "when a test is written", -> ##### Running on CI -It is now easy to run the specs in a CI environment like Travis and AppVeyor. See the [Travis CI For Your Packages](http://blog.atom.io/2014/04/25/ci-for-your-packages.html) and [AppVeyor CI For Your Packages](http://blog.atom.io/2014/07/28/windows-ci-for-your-packages.html) posts for more details. +It is now easy to run the specs in a CI environment like Travis and AppVeyor. See the [Travis CI For Your Packages](https://blog.atom.io/2014/04/25/ci-for-your-packages.html) and [AppVeyor CI For Your Packages](http://blog.atom.io/2014/07/28/windows-ci-for-your-packages.html) posts for more details. ##### Running via the Command Line diff --git a/content/shadow-dom/sections/removing-shadow-dom-styles.md b/content/shadow-dom/sections/removing-shadow-dom-styles.md index e022a9d82a..50fadd325d 100644 --- a/content/shadow-dom/sections/removing-shadow-dom-styles.md +++ b/content/shadow-dom/sections/removing-shadow-dom-styles.md @@ -173,4 +173,4 @@ atom-text-editor .my-class.my-class { #### When should I migrate my theme/package? - If you already want to test the migration on master or Beta channel, make sure to change your `package.json` file to `"engines": { "atom": ">=1.13.0 <2.0.0" }`. This will prevent Atom from updating your theme or package before the user also updates Atom to version `1.13`. -- Or you can wait until Atom `1.13` reaches __Stable__. Check [blog.atom.io](http://blog.atom.io/) to see if `1.13` already has been released. Don't worry if you're a bit late, Atom will transform the deprecated selectors automatically to avoid breaking any themes or packages. But users will start to see a deprecation warning in [deprecation-cop](https://github.com/atom/deprecation-cop). +- Or you can wait until Atom `1.13` reaches __Stable__. Check [blog.atom.io](https://blog.atom.io/) to see if `1.13` already has been released. Don't worry if you're a bit late, Atom will transform the deprecated selectors automatically to avoid breaking any themes or packages. But users will start to see a deprecation warning in [deprecation-cop](https://github.com/atom/deprecation-cop). diff --git a/content/upgrading-to-1-0-apis/sections/upgrading-your-package.md b/content/upgrading-to-1-0-apis/sections/upgrading-your-package.md index 4871049357..659771bc8d 100644 --- a/content/upgrading-to-1-0-apis/sections/upgrading-your-package.md +++ b/content/upgrading-to-1-0-apis/sections/upgrading-your-package.md @@ -608,4 +608,4 @@ atom.workspaceView.command 'core:close core:cancel', -> #### Upgrading your stylesheet's selectors -Many selectors have changed, and we have introduced the [Shadow DOM](http://blog.atom.io/2014/11/18/avoiding-style-pollution-with-the-shadow-dom.html) to the editor. See the [Upgrading Your UI Theme And Package Selectors guide](http://flight-manual.atom.io/upgrading-to-1-0-apis/sections/upgrading-your-ui-theme-or-package-selectors/) for more information in upgrading your package stylesheets. +Many selectors have changed, and we have introduced the [Shadow DOM](https://blog.atom.io/2014/11/18/avoiding-style-pollution-with-the-shadow-dom.html) to the editor. See the [Upgrading Your UI Theme And Package Selectors guide](http://flight-manual.atom.io/upgrading-to-1-0-apis/sections/upgrading-your-ui-theme-or-package-selectors/) for more information in upgrading your package stylesheets. diff --git a/content/upgrading-to-1-0-apis/sections/upgrading-your-syntax-theme.md b/content/upgrading-to-1-0-apis/sections/upgrading-your-syntax-theme.md index d5d7063d9d..c862e81ccd 100644 --- a/content/upgrading-to-1-0-apis/sections/upgrading-your-syntax-theme.md +++ b/content/upgrading-to-1-0-apis/sections/upgrading-your-syntax-theme.md @@ -10,11 +10,11 @@ title: Upgrading Your Syntax Theme ### Upgrading Your Syntax Theme -Text editor content is now rendered in the shadow DOM, which shields it from being styled by global style sheets to protect against accidental style pollution. For more background on the shadow DOM, check out the [Shadow DOM 101](http://www.html5rocks.com/en/tutorials/webcomponents/shadowdom) on HTML 5 Rocks. +Text editor content is now rendered in the shadow DOM, which shields it from being styled by global style sheets to protect against accidental style pollution. For more background on the shadow DOM, check out the [Shadow DOM 101](https://www.html5rocks.com/en/tutorials/webcomponents/shadowdom) on HTML 5 Rocks. Syntax themes are specifically intended to style only text editor content, so they are automatically loaded directly into the text editor's shadow DOM when it is enabled. This happens automatically when the theme's `package.json` contains a `theme: "syntax"` declaration, so you don't need to change anything to target the appropriate context. -When theme style sheets are loaded into the text editor's shadow DOM, selectors intended to target the editor from the *outside* no longer make sense. Styles targeting the `.editor` and `.editor-colors` classes instead need to target the `:host` pseudo-element, which matches against the containing `atom-text-editor` node. Check out the [Shadow DOM 201](http://www.html5rocks.com/en/tutorials/webcomponents/shadowdom-201#toc-style-host) article for more information about the `:host` pseudo-element. +When theme style sheets are loaded into the text editor's shadow DOM, selectors intended to target the editor from the *outside* no longer make sense. Styles targeting the `.editor` and `.editor-colors` classes instead need to target the `:host` pseudo-element, which matches against the containing `atom-text-editor` node. Check out the [Shadow DOM 201](https://www.html5rocks.com/en/tutorials/webcomponents/shadowdom-201#toc-style-host) article for more information about the `:host` pseudo-element. Here's an example from Atom's light syntax theme. Note that the `atom-text-editor` selector intended to target the editor from the outside has been retained to allow the theme to keep working during the transition phase when it is possible to disable the shadow DOM. diff --git a/content/upgrading-to-1-0-apis/sections/upgrading-your-ui-theme-or-package-selectors.md b/content/upgrading-to-1-0-apis/sections/upgrading-your-ui-theme-or-package-selectors.md index 9fe3a6dfd5..785038e9c6 100644 --- a/content/upgrading-to-1-0-apis/sections/upgrading-your-ui-theme-or-package-selectors.md +++ b/content/upgrading-to-1-0-apis/sections/upgrading-your-ui-theme-or-package-selectors.md @@ -41,7 +41,7 @@ Rather than adding classes to standard HTML elements to indicate their role, Ato #### Supporting the Shadow DOM -Text editor content is now rendered in the shadow DOM, which shields it from being styled by global style sheets to protect against accidental style pollution. For more background on the shadow DOM, check out the [Shadow DOM 101](http://www.html5rocks.com/en/tutorials/webcomponents/shadowdom) on HTML 5 Rocks. If you need to style text editor content in a UI theme, you'll need to circumvent this protection for any rules that target the text editor's content. Some examples of the kinds of UI theme styles needing to be updated: +Text editor content is now rendered in the shadow DOM, which shields it from being styled by global style sheets to protect against accidental style pollution. For more background on the shadow DOM, check out the [Shadow DOM 101](https://www.html5rocks.com/en/tutorials/webcomponents/shadowdom) on HTML 5 Rocks. If you need to style text editor content in a UI theme, you'll need to circumvent this protection for any rules that target the text editor's content. Some examples of the kinds of UI theme styles needing to be updated: * Highlight decorations * Gutter decorations @@ -53,7 +53,7 @@ During a transition phase, it will be possible to enable or disable the text edi ##### Shadow DOM Selectors -Chromium provides two tools for bypassing shadow boundaries, the `::shadow` pseudo-element and the `/deep/` combinator. For an in-depth explanation of styling the shadow DOM, see the [Shadow DOM 201](http://www.html5rocks.com/en/tutorials/webcomponents/shadowdom-201#toc-style-cat-hat) article on HTML 5 Rocks. +Chromium provides two tools for bypassing shadow boundaries, the `::shadow` pseudo-element and the `/deep/` combinator. For an in-depth explanation of styling the shadow DOM, see the [Shadow DOM 201](https://www.html5rocks.com/en/tutorials/webcomponents/shadowdom-201#toc-style-cat-hat) article on HTML 5 Rocks. ###### `::shadow` diff --git a/content/using-atom/sections/atom-packages.md b/content/using-atom/sections/atom-packages.md index c297379333..8a58227ae2 100644 --- a/content/using-atom/sections/atom-packages.md +++ b/content/using-atom/sections/atom-packages.md @@ -11,7 +11,7 @@ This means that packages can be incredibly powerful and can change everything fr In order to install a new package, you can use the Install tab in the now familiar Settings View. Open up the Settings View using Cmd+,Ctrl+,, click on the "Install" tab and type your search query into the box under Install Packages. -The packages listed here have been published to http://atom.io/packages which is the official registry for Atom packages. Searching on the Settings View will go to the Atom package registry and pull in anything that matches your search terms. +The packages listed here have been published to https://atom.io/packages which is the official registry for Atom packages. Searching on the Settings View will go to the Atom package registry and pull in anything that matches your search terms. ![Package install screen](../../images/packages-install.png "Package install screen") diff --git a/content/using-atom/sections/basic-customization.md b/content/using-atom/sections/basic-customization.md index a217fb7d93..bf6f1c9cba 100644 --- a/content/using-atom/sections/basic-customization.md +++ b/content/using-atom/sections/basic-customization.md @@ -7,7 +7,7 @@ Now that we are feeling comfortable with just about everything built into Atom, #### Configuring with CSON -All of Atom's config files (with the exception of your [style sheet](#style-tweaks) and your [Init Script](/hacking-atom/sections/the-init-file)) are written in CSON, short for [CoffeeScript Object Notation](https://github.com/bevry/cson#what-is-cson). Just like its namesake JSON, [JavaScript Object Notation](http://json.org/), CSON is a text format for storing structured data in the form of simple objects made up of key-value pairs. +All of Atom's config files (with the exception of your [style sheet](#style-tweaks) and your [Init Script](/hacking-atom/sections/the-init-file)) are written in CSON, short for [CoffeeScript Object Notation](https://github.com/bevry/cson#what-is-cson). Just like its namesake JSON, [JavaScript Object Notation](https://json.org/), CSON is a text format for storing structured data in the form of simple objects made up of key-value pairs. ```coffee key: diff --git a/content/using-atom/sections/find-and-replace.md b/content/using-atom/sections/find-and-replace.md index 02f90e5944..e8cfcb455a 100644 --- a/content/using-atom/sections/find-and-replace.md +++ b/content/using-atom/sections/find-and-replace.md @@ -28,7 +28,7 @@ You can also find and replace throughout your entire project if you invoke the p This is a great way to find out where in your project a function is called, an anchor is linked to or a specific misspelling is located. Click on the matching line to jump to that location in that file. -You can limit a search to a subset of the files in your project by entering a [glob pattern](http://en.wikipedia.org/wiki/Glob_%28programming%29) into the "File/Directory pattern" text box. For example, the pattern `src/*.js` would restrict the search to javascript files in the `src` directory. The "globstar" pattern (`**`) can be used to match arbitrarily many subdirectories. For example, `docs/**/*.md` will match `docs/a/foo.md`, `docs/a/b/foo.md`, etc. +You can limit a search to a subset of the files in your project by entering a [glob pattern](https://en.wikipedia.org/wiki/Glob_%28programming%29) into the "File/Directory pattern" text box. For example, the pattern `src/*.js` would restrict the search to javascript files in the `src` directory. The "globstar" pattern (`**`) can be used to match arbitrarily many subdirectories. For example, `docs/**/*.md` will match `docs/a/foo.md`, `docs/a/b/foo.md`, etc. When you have multiple project folders open, this feature can also be used to search in only one of those folders. For example, if you had the folders `/path1/folder1` and `/path2/folder2` open, you could enter a pattern starting with `folder1` to search only in the first folder. diff --git a/content/using-atom/sections/moving-in-atom.md b/content/using-atom/sections/moving-in-atom.md index a836f4e6cd..95f8134c5d 100644 --- a/content/using-atom/sections/moving-in-atom.md +++ b/content/using-atom/sections/moving-in-atom.md @@ -46,7 +46,7 @@ You can also jump around a little more informatively with the Symbols View. To j ![Search by symbol across your project](../../images/symbol.png) -You can generate a `tags` file by using the [ctags utility](https://ctags.io/). Once it is installed, you can use it to generate a `tags` file by running a command to generate it. See the [ctags documentation](http://docs.ctags.io/en/latest/) for details. +You can generate a `tags` file by using the [ctags utility](https://ctags.io/). Once it is installed, you can use it to generate a `tags` file by running a command to generate it. See the [ctags documentation](https://docs.ctags.io/en/latest/) for details. Once you have your `tags` file generated, you can use it to search for symbols across your project by pressing Cmd+Shift+RCtrl+Shift+R. This also enables you to use Alt+Cmd+DownAlt+Ctrl+Down to go to and Alt+Cmd+UpAlt+Ctrl+Up to return from the declaration of the symbol under the cursor. diff --git a/content/using-atom/sections/version-control-in-atom.md b/content/using-atom/sections/version-control-in-atom.md index 02d0f1976f..70f81cf534 100644 --- a/content/using-atom/sections/version-control-in-atom.md +++ b/content/using-atom/sections/version-control-in-atom.md @@ -3,7 +3,7 @@ title: Version Control in Atom --- ### Version Control in Atom -Version control is an important aspect of any project and Atom comes with basic [Git](http://git-scm.com) and [GitHub](https://github.com) integration built in. +Version control is an important aspect of any project and Atom comes with basic [Git](https://git-scm.com) and [GitHub](https://github.com) integration built in. In order to use version control in Atom, the project root needs to contain the Git repository. diff --git a/layouts/includes/bottom_bar.html b/layouts/includes/bottom_bar.html index a13617b2d9..02fda1a0f6 100644 --- a/layouts/includes/bottom_bar.html +++ b/layouts/includes/bottom_bar.html @@ -4,7 +4,7 @@ diff --git a/layouts/toc.html b/layouts/toc.html index 32e099a5e9..0e2453ed3a 100644 --- a/layouts/toc.html +++ b/layouts/toc.html @@ -2,7 +2,7 @@ <%= renderp '/includes/meta.html' %> - +
diff --git a/outline.md b/outline.md index 6cdb5d4461..b4cc507d91 100644 --- a/outline.md +++ b/outline.md @@ -54,7 +54,7 @@ Here is the remaining outline: * aggregating subscriptions * view best practices * don't make a slow package - * CI for packages (http://blog.atom.io/2014/04/25/ci-for-your-packages.html) + * CI for packages (https://blog.atom.io/2014/04/25/ci-for-your-packages.html) ### Include in Chapter 3 or 4 * Make sure we include (in Ch 3 or Ch4 or both) @@ -63,11 +63,11 @@ Here is the remaining outline: * settings (how to enable the settings button on the package installer) * notifications package * config api - - http://blog.atom.io/2014/10/02/config-api-has-schema.html - - http://blog.atom.io/2014/10/31/language-scoped-config.html + - https://blog.atom.io/2014/10/02/config-api-has-schema.html + - https://blog.atom.io/2014/10/31/language-scoped-config.html - https://atom.io/docs/latest/advanced/scopes-and-scope-descriptors * subscriptions - - http://blog.atom.io/2014/09/16/new-event-subscription-api.html + - https://blog.atom.io/2014/09/16/new-event-subscription-api.html * subscribing to events * subscribing to commands * creating dom elements @@ -83,7 +83,7 @@ Here is the remaining outline: * advanced keymaps (in Guides) * serialization * converting textmate bundles - * decoration (http://blog.atom.io/2014/07/24/decorations.html) + * decoration (https://blog.atom.io/2014/07/24/decorations.html) * modal panel * modal decorations * notifications @@ -99,7 +99,7 @@ Here is the remaining outline: * To core * Opening issues * Roadmaps - - http://blog.atom.io/2014/10/23/public-roadmap.html + - https://blog.atom.io/2014/10/23/public-roadmap.html * Where is the code? * Forum * Building Atom