Understand your Mac and iPhone more deeply by tracing the evolution of Mac OS X from prelease to Swift. John Siracusa delivers the details.
You've got two main options:
# If you don't remember the exact path/name, search the log for deleted files | |
git log --diff-filter=D --summary | grep delete | |
# Find the file you want to get from the ouput, and use the path | |
# Find the commits that involved that path | |
git log --all -- some/path/to/deleted.file | |
# Bring the file back to life to the current repo (sha commit of parent of commit that deleted) | |
git checkout shaofthecommitthatdeletedthefile^ -- some/path/to/deleted.file |
def create_template_pipeline() -> Pipeline: | |
""" Template declareed here with real inputs, but placeholder outputs and parameters """ | |
return Pipeline( | |
[ | |
node( | |
func=create_model_inputs, | |
inputs=[ # These inputs are never overriden | |
"feat_days_since_last_shutdown", | |
"feat_days_between_shutdown_last_maintenance", | |
"feat_fte_maintenance_hours_last_6m", |
Goal: find a Linux alternative to FancyZones for Windows
Name | Recommended | Type | Supports main colum | Supports layouts | Multiple windows in same tile | Windows can span multiple zones | Notes |
---|---|---|---|---|---|---|---|
gSnap | 👍👍 | Gnome extension | yes | yes | yes | yes | Can be configured almost just like FancyZones; in the settings:
|
gTile | Gnome extension | no? | |||||
Tiling Assistant | 👍 | Gnome extension | yes | yes | yes | yes | Layout support is "experimental" and the UX is a bit unintuitive; after enabling layouts, you have to click the star icon beside a layout to mark it as a favourite before you can then hold Alt while dragging |
These examples all live in a default server block in your httpd.conf(5).
server "default" {
listen on * port 80
... # all the location blocks can together right here
}
We'll be using slowcgi(8) as the example, because with the -d
flag it helpfully spits out the FastCGI environment it got from httpd(8) and what it's planning to do with that.
I recently had several days of extremely frustrating experiences with service workers. Here are a few things I've since learned which would have made my life much easier but which isn't particularly obvious from most of the blog posts and videos I've seen.
I'll add to this list over time – suggested additions welcome in the comments or via twitter.com/rich_harris.
Chrome 51 has some pretty wild behaviour related to console.log
in service workers. Canary doesn't, and it has a load of really good service worker related stuff in devtools.