To setup your computer to work with *.test domains, e.g. project.test, awesome.test and so on, without having to add to your hosts file each time.
- Homebrew
- Mountain Lion -> High Sierra
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/usr/bin/env python3 | |
import zipfile | |
import sys | |
import re | |
import xml.etree.ElementTree as ET | |
namespaces = { | |
'a': 'http://schemas.openxmlformats.org/drawingml/2006/main', | |
'r': 'http://schemas.openxmlformats.org/officeDocument/2006/relationships', |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#r "nuget:Microsoft.ML" | |
#r "nuget:Microsoft.ML.OnnxRuntime" | |
#r "nuget:Microsoft.ML.OnnxTransformer" | |
#r "nuget:Microsoft.ML.ImageAnalytics" | |
#r "nuget:System.Drawing.Common" | |
open System.IO | |
open System.Drawing | |
open Microsoft.ML | |
open Microsoft.ML.Data |
Goals: Add links that are reasonable and good explanations of how stuff works. No hype and no vendor content if possible. Practical first-hand accounts and experience preferred (super rare at this point).
Originally written 2020-05-16
dune-release
is a good improvement over the old opam-publish
, but releasing
software is still clearly not a solved problem, and I find it hard to remember
the exact steps involved in releasing an opam package, especially if some time
has passed since the last release. This note is an attempt at having a place
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Powershell script to export Powerpoint Presentations to pdf using the Powerpoint COM API | |
# Based on a VB script with the same purpose | |
# http://superuser.com/questions/641471/how-can-i-automatically-convert-powerpoint-to-pdf | |
function Export-Presentation($inputFile) | |
{ | |
# Load Powerpoint Interop Assembly | |
[Reflection.Assembly]::LoadWithPartialname("Microsoft.Office.Interop.Powerpoint") > $null | |
[Reflection.Assembly]::LoadWithPartialname("Office") > $null |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
## Put this Makefle in your project directory---i.e., the directory | |
## containing the paper you are writing. Assuming you are using the | |
## rest of the toolchain here, you can use it to create .html, .tex, | |
## and .pdf output files (complete with bibliography, if present) from | |
## your markdown file. | |
## - Using `make` without arguments will generate html, tex, and pdf | |
## output files from all of the files with the designated markdown | |
## extension. The default is `.md` but you can change this. | |
## - You can specify an output format with `make tex`, `make pdf` or | |
## - `make html`. |
NewerOlder