! #tell git that this isn't an internal alias, but should be run as a bash command
f() { #create a bash function called "f"
echo \" #print the string we're creating (added backslash now in breakdown for syntax highlighting to look better)
https:// #start the url with "https://"
$( #start a subcommand
git config #git config makes it easy to read repository settings
--get #get a setting...
remote.origin.url #...called remote.origin.url
| #pipe the output of the git config command to...
function main() { | |
if (app.documents.length) { | |
var outputDir = Folder.selectDialog('Select output folder.', '~'); | |
if (outputDir) { | |
for (var i = 0; i < app.documents.length; i++) { | |
doc = app.documents[i]; |
#!/usr/bin/env bash | |
function cleanup() { | |
rm -rf "$temp_dir" > /dev/null 2>&1 | |
} | |
trap cleanup EXIT | |
function setup() { | |
temp_dir='/tmp/imgcmprs' |
require('js-yaml'); | |
var _ = require('lodash'); | |
var fs = require('fs'); | |
var aws = require('aws-sdk'); | |
var path = require('path'); | |
var exec = require('exec-sync'); | |
module.exports = function (grunt) { | |
grunt.initConfig({ |
r.js -o cssIn=flat.css out=flat_result.css | |
r.js -o cssIn=import.css out=import_result.css |
Know your element (__
) from your modifier (--
). Both blocks and elements can have modifiers. (.b--m
, .b__e--m
).
In react lingo, BEM's "B" (for "Block") is a component.
Elements can nest deep in html, but the selector doesn't represent this deep nesting. (no .a__b__c
, instead just .a__c
- which can be in .a__b
).
The idea
The idea with BEM is to keep a flat hierarchy (don't nest selectors) with simple selectors - only one class per selector, and no IDs or element tags. By not nesting we have a low and consistent specificity of all html elements, which makes it possible to have modifications of styles without using !important
.
MidiIn min; | |
MidiOut mou; | |
MidiMsg msg; | |
2 => int input_device; | |
1 => int output_device; | |
if( me.args() ) me.arg(0) => Std.atoi => input_device; | |
if( me.args() ) me.arg(1) => Std.atoi => output_device; |
server { | |
listen 8999 default_server; | |
server_name _; | |
location / { | |
# return 418; #teacup for test | |
proxy_set_header X-Real-IP $remote_addr; | |
proxy_set_header X-Forwarded-For $remote_addr; | |
proxy_set_header Host $host; | |
proxy_pass http://127.0.0.1:8080; |
I hereby claim:
- I am magnusdahlstrand on github.
- I am magnus (https://keybase.io/magnus) on keybase.
- I have a public key whose fingerprint is 462F F191 9AFD EF1E CEE8 BD80 C30C BBD9 39B4 3536
To claim this, I am signing this object:
This repository highlights an issue combining next-sitemap with next export when hosting on a static host.
See the thread which prompted this repo
Setup
[email protected], outputs its sitemap to the public directory.
I followed the next documentation for export and have set my npm build script to next build && next export
.
and I followed the next-sitemap documentation instructing me to define a postbuild npm command to trigger the sitemap building.
Problem