| # $ brew install pyenv #pay attention to caveats ($ brew info pyenv) | |
| # $ brew install pyenv-virtualenv | |
| # this goes into .zshrc | |
| export PYENV_ROOT=/usr/local/var/pyenv | |
| if which pyenv > /dev/null; then eval "$(pyenv init -)"; fi | |
| if which pyenv-virtualenv-init > /dev/null; then eval "$(pyenv virtualenv-init -)"; fi |
| // Colors reference | |
| // You can use the following as so: | |
| // console.log(colorCode, data); | |
| // console.log(`${colorCode}some colorful text string${resetCode} rest of string in normal color`); | |
| // | |
| // ... and so on. | |
| export const reset = "\x1b[0m" | |
| export const bright = "\x1b[1m" | |
| export const dim = "\x1b[2m" |
Minimal example: transcode from MP3 to WMA:
ffmpeg -i input.mp3 output.wma
You can get the list of supported formats with:
ffmpeg -formats
Convert WAV to MP3, mix down to mono (use 1 audio channel), set bit rate to 64 kbps and sample rate to 22050 Hz:
From time to time, Musk will send out an e-mail to the entire company to enforce a new policy or let them know about something that's bothering him. One of the more famous e-mails arrived in May 2010 with the subject line: Acronyms Seriously Suck:
There is a creeping tendency to use made up acronyms at SpaceX. Excessive use of made up acronyms is a significant impediment to communication and keeping communication good as we grow is incredibly important. Individually, a few acronyms here and there may not seem so bad, but if a thousand people are making these up, over time the result will be a huge glossary that we have to issue to new employees. No one can actually remember all these acronyms and people don't want to seem dumb in a meeting, so they just sit there in ignorance. This is particularly tough on new employees.
That needs to stop immediately or I will take drastic action - I have given enough warning over the years. Unless an acronym is approved by me, it should not enter the SpaceX glossary.
| curl -I -X OPTIONS \ | |
| -H "Origin: http://EXAMPLE.COM" \ | |
| -H 'Access-Control-Request-Method: GET' \ | |
| http://EXAMPLE.COM/SOMETHING 2>&1 | grep 'Access-Control-Allow-Origin' |
| // async/await"able" DOM event handlers | |
| async function getMeSomeData() { | |
| // ... | |
| return data | |
| } | |
| document.addEventListener('DOMContentLoaded', async () => { | |
| const someContainer = document.getElementById('someContainer'); |
The idea here is that some of us always want line numbers but never want to add a "line-numbers" class to our HTML. This tweaked version of the plugin always adds the line numbers to any <pre> block that also has a language class that Prism will be highlighting.
To keep you from being boxed in, I've added an option to use the pre class to opt out by setting class = "no-line-numbers". If you are much more likely to want line numbers than to not want them, then this is the better way of doing things. If you think you usually don't want line numbers, then just use the plugin straight from Prism.
You should add this file after the main prism.js file on your page. Do not include the line-numbers plugin when you download Prism because you want this one to do the work and not conflict with the official one.
This may break at any time as the Prism.js teams changes the base functionality of the highlighter or the line numbers plugin.
| .next | |
| out |
As I'm writing this small tutorial, I assume you've read my previous one about setting up macOS, so if for any tool I'll use without explanation, look to that other article.
The full version IS NOT MANDATORY, as in the tutorial that follows I installed the smaller version of MacTeX and proceded installing every needed dependency. Installing the complete package is about ~3.5GB of download and ~5GB on disk, the smaller one is just about 80MBs.
Click here to download the complete version or here to download the smaller version.
