- Install target mingw-w64:
brew install mingw-w64
- Add target to rustup:
rustup target add x86_64-pc-windows-gnu
- Create
.cargo/config
- Add the instructions below to
.cargo/config
[target.x86_64-pc-windows-gnu]
name: Security audit | |
on: | |
schedule: | |
- cron: '0 0 * * *' | |
push: | |
paths: | |
- '**/Cargo.toml' | |
- '**/Cargo.lock' | |
jobs: | |
security_audit: |
brew install mingw-w64
rustup target add x86_64-pc-windows-gnu
.cargo/config
.cargo/config
[target.x86_64-pc-windows-gnu]
{ | |
"env": { | |
"browser": true | |
}, | |
"parserOptions": { | |
"ecmaVersion": 5 | |
}, | |
"globals": { | |
"$A": true, | |
"AuraContext": true, |
Some notes on how to setup various open-source XMR Miners on Ubuntu 16
# Proudly supplied by Salesforce Way Site: https://salesforceway.com | |
# This cheatsheet contains the most often used SFDX commands for beginners to get a jumpstart. | |
# Hint. it is highly recommended to use `-h` to check the usage of any SFDX commands and corresponding parameters. | |
# For instance, use `sfdx force:auth:web:login -h` to checke what `-d` `-a` parameters do | |
# List down all supported dx commands: | |
sfdx force:doc:commands:list | |
# Check current DebHub and Scratch Org status | |
sfdx force:org:list |
export ORG_ALIAS='DummyScratchOrg' | |
export PROJECT_NAME='DummyProject' | |
export PERMISSION_SET='DummyPermSet' | |
export IMPORT_PLAN='Dummy-plan.json' | |
# Create a Salesforce DX project | |
sfdx force:project:create -n $PROJECT_NAME | |
# Regist development/sandbox org | |
sfdx force:auth:web:login [-d] -a $ORG_ALIAS |
function setjdk | |
if test -n "$JAVA_HOME" | |
removeFromPath "$JAVA_HOME/bin" | |
end | |
set -gx JAVA_HOME (/usr/libexec/java_home -v $argv[1]) | |
set -gx PATH $JAVA_HOME/bin $PATH | |
end | |
function removeFromPath | |
set -l idx 0 |
Emacs packages, features, files, layers, extensions, auto-loading, require
,
provide
, use-package
… All these terms getting you confused? Let’s clear up
a few things.
Emacs files contains code that can be evaluated. When evaluated, the functions, macros and modes defined in that file become available to the current Emacs session. Henceforth, this will be termed as loading a file.
One major problem is to ensure that all the correct files are loaded, and in the
// Promise.all is good for executing many promises at once | |
Promise.all([ | |
promise1, | |
promise2 | |
]); | |
// Promise.resolve is good for wrapping synchronous code | |
Promise.resolve().then(function () { | |
if (somethingIsNotRight()) { | |
throw new Error("I will be rejected asynchronously!"); |
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.