find, filter, execute... , grep, replace
find ./data -type f -name "*.csv" -exe cat {} \; | grep "andres" | sed '/ //g'
the same thing broken down by each action
const REL_PATH = '..'; | |
const ASSET_DIR = 'assets'; | |
const IMAGE_DIR = 'images'; | |
// THIS ONE WORKS | |
function testVariableRequire() { | |
var name = 'pause_button.png'; | |
var button_module = new Icon('test', require(`./${REL_PATH}/${ASSET_DIR}/${IMAGE_DIR}/${name}`), 70, 119); |
find, filter, execute... , grep, replace
find ./data -type f -name "*.csv" -exe cat {} \; | grep "andres" | sed '/ //g'
the same thing broken down by each action
//// | |
/// @group layout | |
//// | |
/// | |
/// @name max_width | |
/// @description Insert media content when less than target width | |
/// @param {number} $width [max width value] | |
@mixin max_width($width) { | |
@media screen and (max-width: #{$width}) { |
// THE URL FOR THE MAIN INSTAGRAM IMAGE DOES NOT TRIGGER THE DOWNLOAD EVENT | |
// INSTEAD IT OPENS THE IMAGE IN A NEW TAB | |
// RUNNING THE SCRIPT THE SECOND TIME TRIGGERS THE DOWNLOAD EVENT | |
// KEYBOARD SHORTCUT MAKES THIS TWO STEP PROCESS VERY QUICK | |
// Step 1: `ctrl`+`shift`+`i` -> `ctrl`+`enter` | |
// Step 2: `ctrl`+`enter` | |
var filename = ''; | |
var target = ''; |
The standard code style linter is a great tool by Feross - check it out!
Remove trailing semicolons:
find . -path ./node_modules -prune -o -type f -name '*.js' -exec sed -i '' -e 's/;$//' {} \;
Ensure space between function
and opening bracket:
Standard Readme Style
Your README file is normally the first entry point to your code. It should tell people why they should use your module, how they can install it, and how they can use it. Standardizing how you write your README makes creating and maintaining your READMEs easier. Great documentation takes work!
This repository contains:
#!/bin/sh | |
# | |
# a simple way to parse shell script arguments | |
# | |
# please edit and use to your hearts content | |
# | |
ENVIRONMENT="dev" |