| Instance | Branch |
|---|
| { | |
| // Name of the location | |
| "name": "Drewry and Cactus-Gardenia Court", | |
| // The URI of the location, locations are groups of stops - they can be | |
| // intersections, stations or even specific addresses. | |
| // generally a Location has more then one stop, but sometimes there are | |
| // stops without an opposing direction stop and sits in a location by itself. | |
| // | |
| // Notes: |
| package main | |
| import "code.google.com/p/go-tour/pic" | |
| func Pic(dx, dy int) [][]uint8 { | |
| // Allocate two-dimensioanl array. | |
| a := make([][]uint8, dy) | |
| for i := 0; i < dy; i++ { | |
| a[i] = make([]uint8, dx) | |
| } |
| package main | |
| import "fmt" | |
| // fibonacci is a function that returns | |
| // a function that returns an int. | |
| func fibonacci() func() int { | |
| f2, f1 := 0, 1 | |
| return func() int { | |
| f := f2 |
| package main | |
| /* | |
| URL: https://github.com/mccoyst/myip/blob/master/myip.go | |
| URL: http://changsijay.com/2013/07/28/golang-get-ip-address/ | |
| */ | |
| import ( | |
| "net" | |
| "os" |
| import logging | |
| from traceback import format_exc | |
| import datetime | |
| from schedule import Scheduler | |
| logger = logging.getLogger('schedule') |
Fonte: http://brandon.invergo.net/news/2012-05-26-using-gnu-stow-to-manage-your-dotfiles.html?round=two
I accidentally stumbled upon something yesterday that I felt like sharing, which fell squarely into the "why the hell didn't I know about this before?" category. In this post, I'll describe how to manage the various configuration files in your GNU/Linux home directory (aka "dotfiles" like .bashrc) using GNU Stow.
The difficulty is that it would be helpful to manage one's configuration files with a version control system like Git, Mercurial or Bazaar, but many/most dotfiles reside at the top-level of your home directory, where it wouldn't be a good idea to initialize a VCS repository. Over time I've come across various programs which aim to manage this for you by keeping all the files in a subdirectory and then installing or linking them into their appropriate places. None of those programs ever really appealed to me. They would require a ton of dependencies (like Ruby and a ton of libraries for it) or t
While this gist has been shared and followed for years, I regret not giving more background. It was originally a gist for the engineering org I was in, not a "general suggestion" for any React app.
Typically I avoid folders altogether. Heck, I even avoid new files. If I can build an app with one 2000 line file I will. New files and folders are a pain.