flying-sheep

#!/usr/bin/env python3

import re
from contextlib import closing
from epub import create_epub, DEFAULT_STYLESHEET

import requests
import requests_cache
from bs4 import BeautifulSoup
from smartypants import smartypants

mac2000

<#
.Synopsis
   Converts a PowerShell object to a Markdown table.
.EXAMPLE
   $data | ConvertTo-Markdown
.EXAMPLE
   ConvertTo-Markdown($data)
#>
Function ConvertTo-Markdown {
    [CmdletBinding()]

jesseschalken

My preferred code style is 2-space K&R. This is intended to provide a justification for this style.

Why K&R?

K&R style has the following properties:

1. Provides symmetric size (in terms of screen space consumed) between the opening and closing syntax of a clode block.
2. Forces no empty or meaningless lines, thereby avoiding artificial distance between related things that should be together.
3. Consumes the minimum vertical space while keeping the opening and closing syntax of a block on separate lines from the content.

Jaykul

# It might work in 4, but I'm not testing there. Lower you'll have to tweak code
#requires -Version 5.0
param(
    # Your Live ID for MSDN login
    [Parameter(Mandatory)]
    [PSCredential]
    [System.Management.Automation.CredentialAttribute()]
    $Credential,

    # Pick a browser to use. Defaults to Firefox (which doesn't seem to require an external Driver file) 

joelverhagen

[no Search()] nuget.exe list
[no Search()] nuget.exe list -allversions
[no Search(), no IsAbsoluteLatestVersion] nuget.exe list
[no Search(), no IsAbsoluteLatestVersion] nuget.exe list -allversions
  GET /api/v2/Packages HTTP/1.1
  GET /api/v2/Packages?$skip=100 HTTP/1.1

[no Search()] nuget.exe list -allversions -prerelease
[no Search(), no IsAbsoluteLatestVersion] nuget.exe list -allversions -prerelease
  GET /api/v2/Packages()?$orderby=Id&$skip=0&$top=30 HTTP/1.1

giordanocardillo

1. Open a command prompt as Administrator
2. In the command prompt, type the following:

• Office 2016 (32-bit) on a 32-bit version of Windows

  cscript "C:\Program Files\Microsoft Office\Office16\OSPP.VBS" /dstatus

• Office 2016 (32-bit) on a 64-bit version of Windows

  cscript "C:\Program Files (x86)\Microsoft Office\Office16\OSPP.VBS" /dstatus

• Office 2016 (64-bit) on a 64-bit version of Windows

evoelker

function Sleep-Progress($seconds)
{
     <#
     .SYNOPSIS
     Function to Start-Sleep with a progress bar

     .DESCRIPTION
     Runs the 'Start-Sleep' command using the with a progress bar. Time is passed to the function in seconds as an argument.

     .NOTES

brettmillerb

# escape=`
ARG fromTag=latest
ARG WindowsServerCoreRepo=mcr.microsoft.com/windows/servercore

# Use server core as an installer container to extract PowerShell,
# As this is a multi-stage build, this stage will eventually be thrown away
FROM ${WindowsServerCoreRepo}:${fromTag} AS installer-env

ARG PS_VERSION=6.2.0
ARG PS_PACKAGE_URL=https://github.com/PowerShell/PowerShell/releases/download/v${PS_VERSION}/PowerShell-${PS_VERSION}-win-x64.zip

Jaykul

Using Nerd Fonts in PowerShell

I've been recommending people use NerdFonts in their terminals for a while, but using the extra characters ends up being rather a pain. I have to look up characters in their web cheat-sheet, and then I either end up with a whole bunch of "$([char]0xf1ed)$([char]0xf00d)" in my profile scripts, which is impossible to read, or I have to translate the hex to decimal so I can type the ALT codes in my editor...

So today I fixed it, using PANSIES (the PowerShell ANSI Escape Sequences module).

PANSIES has &entities;

In PANSIES output (i.e. via the Write-Host, or by using New-Text in a string), you can embed named entities like in html. But unlike HTML, Pansies entities are extensible. So I wrote a little script to re-use the css names for the nerd-font characters and generate entities.

joegasper

<#
.SYNOPSIS
Fast conversion of Microsoft Stream VTT subtitle file to SRT format.
.DESCRIPTION
Uses select-string instead of get-content to improve speed 2 magnitudes.
.PARAMETER Path
Specifies the path to the VTT text file (mandatory).
.PARAMETER OutFile
Specifies the path to the output SRT text file (defaults to input file with .srt).
.EXAMPLE