CharlesNepote

Comparison of syntax extensions in Markdown flavors

I created a crude comparison of the syntax of the various common Markdown extensions to have a better view on what are the most common extensions and what is the most widely accepted syntax for them. The list of Markdown flavors that I looked at was based on the list found on CommonMark's GitHub Wiki.

Flavor	Superscript	Subscript	Deletion* Strikethrough	Insertion*	Highlight*	Footnote	Task list	Table	Abbr	Deflist	Smart typo	TOC	Math	Math Block	Mermaid
GFM

CharlesNepote

# get total requests by status code
awk '{print $9}' /var/log/nginx/access.log | sort | uniq -c | sort -rn

# get top requesters by IP
awk '{print $1}' /var/log/nginx/access.log | sort | uniq -c | sort -rn | head | awk -v OFS='\t' '{"host " $2 | getline ip; print $0, ip}'

# get top requesters by user agent
awk -F'"' '{print $6}' /var/log/nginx/access.log | sort | uniq -c | sort -rn | head

# get top requests by URL

CharlesNepote

#!/bin/bash

CLEAR='\033[0m'
RED='\033[0;31m'

function usage() {
  if [ -n "$1" ]; then
    echo -e "${RED}👉 $1${CLEAR}\n";
  fi
  echo "Usage: $0 [-n number-of-people] [-s section-id] [-c cache-file]"

CharlesNepote

#!/usr/bin/env bash

# This script runs all of the boilerplate commands that I repeatedly need to run
# when submitting a pull request for typical javascript projects.
# To summarize what this script does:
#  - Opens github page to submit a PR in the web browser
#  - Runs linting, tries to fix any errors, then automatically pushes the fixes
#    up. You may need to make some fixes manually.
#  - Runs jest tests. Of course, the CI server would also run these, but I prefer
#    to run them locally as well. That way I can get told my tests are failing

CharlesNepote

#

Simply modify the three following strings for node, ways and relations
newer than="2013-05-28T00:00:00Z

This script is for statistics. For example, it does not extract all nodes from a way if only one node is modified, since the way object and other nodes are not affected.

If you want only the nodes, you only keep the first section of the script where the nodes are extracted.

The polygon-query bounds is to clip the CAP103 area, extracting info only for this area.

CharlesNepote

Download OSM Data

Overpass-Turbo has an easy method to obtain current data. Modify and run the following script:

<!--
This script finds charging_station in Isère.
For other objects, see: http://wiki.openstreetmap.org/wiki/Map_Features
-->