Best way seems to be via a .reg
file.
Which allows for a simple syntax of declaring Registry Changes, which can then be run via the command line.
Example File:
Best way seems to be via a .reg
file.
Which allows for a simple syntax of declaring Registry Changes, which can then be run via the command line.
Example File:
/** | |
* This example shows how we can can preform some check multiple times, and if it | |
* fails we wait a predetermined amount of time and try again. Only returning | |
* once there is a successful attempt. | |
* | |
* This can be useful such as preforming a startup check if you have a Database | |
* Also starting up at the same time, and want rather simple logic to wait on | |
* the database fully starting up. | |
* |
/** | |
* Converts a 'tokens' array into a spec that can be dropped into your spec file. | |
* Assuming a setup with the following: | |
* `let { tokens } = grammar.tokenizeLine("your test text here"); const convert = require("convert-tokens-to-spec.js"); convert(tokens);` | |
*/ | |
module.exports = | |
function convertTokensToSpec(tokens) { | |
let textOutput = ""; |
It's no secret that Pulsar since inherited from Atom, is a big and complex application.
With many discrete, moving aspects, that not all developers have a concrete grasp on. The goal of this document is to make the architecture of Pulsar, as well as the logical flow more understandable and approachable.
This will be accomplished through a series of illustrations detailing the functional decomposition and detailed logical flow of Pulsar and it's parts, as well as lists of what's accomplished in each part.
This is a short document, intended to be eventually transfered to the new Pulsar Documentation site.
When you create a Pulsar Package, there are several package naming conventions that can assist you into making sure your package is discoverable and it's intent is easily understood.
SERVICE-snippets
: Appending -snippets
to the end of a package name indicates this package only provides snippets of the
afformentioned service.autocomplete-SERVICE
: Prepending autocomplete-
to the beginning of a package name indicates this package only providesThe files you care about will be:
Within these files are links to every repo Atom owns, that within their config have "has_wiki": true
Now this doesn't mean that wiki has anything in it, but should still be checked.