to print the file filename.pdf
using the default printer:
lpr filename.pdf
you can also specify the printer name using -P printername
:
lpr -P printername filename.pdf
Direct copy of pre-encoded file:
$ ffmpeg -i filename.mp4 -codec: copy -start_number 0 -hls_time 10 -hls_list_size 0 -f hls filename.m3u8
ffmpeg -i input.mp4 -c copy -ss 00:04:25.000 -to 00:09:25.000 output.mp4 |
'use strict' | |
// ideal for use with AWS Lambda and native Node.js modules | |
// requires Docker: https://docs.docker.com/engine/installation/ | |
/* | |
Usage: | |
node docker-npm.js install | |
node docker-npm.js rebuild |
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.
### Full command line options | |
``` | |
ffmpeg -f gif -i FOO.gif -pix_fmt yuv420p -c:v libx264 -movflags +faststart -filter:v crop='floor(in_w/2)*2:floor(in_h/2)*2' BAR.mp4 | |
``` | |
### Notie | |
* output mp4 is encoded with h264, support Firefox/Chrome/Safari in Windows, Mac OSX, Android, and iOS. |
THREE.TransformationShader = { | |
defines: {}, | |
uniforms: { | |
"tDiffuse": { type: "t", value: texture }, | |
"opacity": { type: "f", value: 1.0 }, | |
"translationX": { type: "f", value: 1.0 }, | |
"translationY": { type: "f", value: 1.0 }, | |
"translationZ": { type: "f", value: 1.0 }, | |
"scaleX": { type: "f", value: 1.0 }, |
* { | |
font-size: 12pt; | |
font-family: monospace; | |
font-weight: normal; | |
font-style: normal; | |
text-decoration: none; | |
color: black; | |
cursor: default; | |
} |
I've heard this before:
What I really get frustrated by is that I cannot wrap
console.*
and preserve line numbers
We enabled this in Chrome DevTools via blackboxing a bit ago.
If you blackbox the script file the contains the console log wrapper, the script location shown in the console will be corrected to the original source file and line number. Click, and the full source is looking longingly into your eyes.