git clone [email protected]:YOUR-USERNAME/YOUR-FORKED-REPO.git
cd into/cloned/fork-repo
git remote add upstream git://github.com/ORIGINAL-DEV-USERNAME/REPO-YOU-FORKED-FROM.git
git fetch upstream
git clone [email protected]:YOUR-USERNAME/YOUR-FORKED-REPO.git
cd into/cloned/fork-repo
git remote add upstream git://github.com/ORIGINAL-DEV-USERNAME/REPO-YOU-FORKED-FROM.git
git fetch upstream
from bs4 import BeautifulSoup as bs | |
import requests | |
def stars_count(url): | |
html = requests.get(url).text | |
soup = bs(html, 'lxml') | |
stars_class = "social-count js-social-count" | |
stars = soup.find('a', class_=stars_class).text.strip() | |
return stars |
#include <stdio.h> | |
#define ___VERSION 406001 | |
#include "gambit.h" | |
#include "somescheme.h" | |
#define SCHEME_LIBRARY_LINKER ____20_somescheme__ | |
___BEGIN_C_LINKAGE |
"use strict"; | |
// module UnderscoreFFI | |
exports.map = function(f) { | |
return function (arr) { | |
return require('underscore').map(arr, f); | |
}; | |
}; |
local lpeg = require'lpeg' | |
local P, R, S = lpeg.P, lpeg.R, lpeg.S --patterns | |
local C, Ct = lpeg.C, lpeg.Ct --capture | |
local V = lpeg.V --variable | |
local parser = P { | |
'program', -- initial rule | |
program = Ct(V'sexpr' ^ 0), | |
wspace = S' \n\r\t' ^ 0, | |
atom = V'boolean' + V'integer' + V'string' + V'symbol', |
(Inspired by https://medium.com/@icanhazedit/clean-up-unused-github-rpositories-c2549294ee45#.3hwv4nxv5)
Open in a new tab all to-be-deleted github repositores (Use the mouse’s middle click or Ctrl + Click) https://github.com/username?tab=repositories
Use one tab https://chrome.google.com/webstore/detail/onetab/chphlpgkkbolifaimnlloiipkdnihall to shorten them to a list.
Save that list to some path
The list should be in the form of “ur_username\repo_name” per line. Use regex search (Sublime text could help). Search for ' |.*' and replace by empty.
#!/usr/bin/env nix-shell | |
#!nix-shell -i bash -p bind.dnsutils -p traceroute -p curl | |
# impure: needs ping | |
#source: https://s3.amazonaws.com/aws-cloudfront-testing/CustomerTesting.html | |
function _e { | |
echo "> $@" | |
eval "$@" 2>&1 | sed -e "s/^/ /" | |
printf "Exit: %s\n\n\n" "$?" | |
} |
Here's a list of links to resources to accompany the "Introduction to JAMstack" video on freeCodeCamp, by Phil Hawksworth
JRM's Syntax-rules Primer for the Merely Eccentric | |
In learning to write Scheme macros, I have noticed that it is easy to | |
find both trivial examples and extraordinarily complex examples, but | |
there seem to be no intermediate ones. I have discovered a few tricks | |
in writing macros and perhaps some people will find them helpful. | |
The basic purpose of a macro is *syntactic* abstraction. As functions | |
allow you to extend the functionality of the underlying Scheme | |
language, macros allow you to extend the syntax. A well designed |