| #!/bin/bash | |
| USER=${1:-sebble} | |
| STARS=$(curl -sI https://api.github.com/users/$USER/starred?per_page=1|egrep '^Link'|egrep -o 'page=[0-9]+'|tail -1|cut -c6-) | |
| PAGES=$((658/100+1)) | |
| echo You have $STARS starred repositories. | |
| echo |
FWIW: I (@rondy) am not the creator of the content shared here, which is an excerpt from Edmond Lau's book. I simply copied and pasted it from another location and saved it as a personal note, before it gained popularity on news.ycombinator.com. Unfortunately, I cannot recall the exact origin of the original source, nor was I able to find the author's name, so I am can't provide the appropriate credits.
I am working on adding support for building and distributing (via PyPI) Python Wheels with C Extensions to the Python wheel and pip packages. The discussion on Distutils-SIG continues, but I believe it is fairly certain that some effort to correctly identify Linux distributions will need to be made. I've begun efforts to add this support to wheel.
If you have a Linux distribution or version of a listed distribution not in this gist, or one of the ones I have not directly verified, I could use the following:
/etc/os-release, if it exists
| #!/bin/sh -e | |
| # | |
| # NOTE: Since Docker 1.10 (February 4, 2016), it has been possible to configure the | |
| # Docker daemon using a JSON config file. On Linux, this file is normally located at | |
| # /etc/docker/daemon.json. You should use this JSON config method if you are running | |
| # a version of Docker that is at least 1.10! | |
| # Here is an example configuration that sets the docker0 bridge IP to 192.168.254.1/24: | |
| # { | |
| # "bip": "192.168.254.1/24" | |
| # } |
영어지만, 조금 더 상세하게 마크다운 사용법을 안내하고 있는
"Markdown Guide (https://www.markdownguide.org/)" 를 보시는 것을 추천합니다. ^^
아, 그리고 마크다운만으로 표현이 부족하다고 느끼신다면, HTML 태그를 활용하시는 것도 좋습니다.
| //usr/bin/env go run $0 "$@"; exit | |
| package main | |
| import ( | |
| "fmt" | |
| "os" | |
| ) | |
| func main() { | |
| fmt.Println("Hello world!") |
Comparison of the performance of FFI vs XS zeromq bindings. For FFI the
ZMQ::FFI bindings are used, first using FFI::Raw on the backend and then
using FFI::Platypus. For XS ZMQ::LibZMQ3 is used.
Comparison is done using the zeromq weather station example, first by timing
wuclient.pl using the various implementations, and then by profiling
wuserver.pl using Devel::NYTProf. When profiling the server is changed to
simply publish 1 million messages and exit.
| #!/usr/bin/env perl | |
| use Mojolicious::Lite; | |
| use DBIx::Sunny; | |
| app->attr(dbh => sub { DBIx::Sunny->connect('dbi:mysql:dbname=bbs', 'root','') }); | |
| get '/' => sub { | |
| my $c = shift; | |
| my $entries = app->dbh->select_all('SELECT * FROM entry'); |
| export GOPATH="$(builtin cd "$(dirname "${BASH_SOURCE[0]:-$_}" )" && pwd)" | |
| export OLDPS1=$PS1 | |
| export PS1="[go:$(basename $GOPATH)] $PS1" | |
| alias gcd="cd $GOPATH" | |
| deactivate() { | |
| export PS1=$OLDPS1 | |
| unset GOPATH | |
| unset OLDPS1 | |
| unalias gcd | |
| unset deactivate |
| #!/bin/bash | |
| # where to store the sparse-image | |
| WORKSPACE=~/Documents/workspace.dmg.sparseimage | |
| create() { | |
| hdiutil create -type SPARSE -fs 'Case-sensitive Journaled HFS+' -size 60g -volname workspace ${WORKSPACE} | |
| } | |
| detach() { |
