lyndsysimon

/* Protonmail cleanup scripts
 * Works with ProtonMail v4.0.14 as of 2022-01-23
 * 
 * Based on Lyndsy's Protonmail mass archiver:
 *     https://gist.github.com/lyndsysimon/e6a4a1becaddf09fe02c503793b545d6
 * 
 * Usage:
 *	- Navigate to your inbox (or another folder/label, presumably)
 *	- Open your browser's developer tools' Javascript console
 *	- Paste in this script

roberth

/*
  minimod: A stripped down module system

  TODO Comparison:
    - [ ] Come up with a benchmark "logic" using plain old functions and let bindings
    - [ ] Write the benchmark for the module system
    - [ ] Write the benchmark for POP?
    - [ ] Qualitative comparison of extensibility in the context of composable
          Nixpkgs packaging logic
  TODO Fine-tuning:

SuperSandro2000

#!/usr/bin/env bash

# shellcheck disable=SC2034
COMMIT_MSG_FILE=$1 # file which contains the commmit message
# shellcheck disable=SC2034
COMMIT_SOURCE=$2 # eg commit
# shellcheck disable=SC2034
SHA1=$3 # eg head

perl -i -ne 'print unless(m/^. Please enter the commit message/..m/^#$/)' "$COMMIT_MSG_FILE"

gnprice

#!/bin/bash
set -eu

usage() {
    cat >&2 <<'EOF'
usage: ./difflog $out1 $out2

Compare two Nix build logs, normalizing out boring differences.

This can be useful to test the effect of a change to build scripts,

anna328p

Arch Installation Guide for Total Beginners

Guide by anna328p/alienpirate5.

This is meant as a companion for the official Arch install guide: https://wiki.archlinux.org/index.php/Installation_guide

This document is a guide for installing Arch Linux from the live system booted with the official installation image.

This document will walk you through the Arch Linux installation process based on the Arch Wiki installation guide. You will need to refer to the wiki for links; this guide just explains the steps in more detail. Keep in mind that this

danbst

{ config, pkgs, lib, ... }: {
  imports = [
    (import <nixpkgs/nixos/modules/system/etc/etc.nix>)
  ];

  options.system.build.etc = lib.mkOption { type = lib.types.package; };
  options.system.activationScripts.etc =
    lib.mkOption { type = lib.types.unspecified; };

  config = {

jimmychu0807

use std::str;

fn main() {
  // -- FROM: vec of chars --
  let src1: Vec<char> = vec!['j','{','"','i','m','m','y','"','}'];
  // to String
  let string1: String = src1.iter().collect::<String>();
  // to str
  let str1: &str = &src1.iter().collect::<String>();
  // to vec of byte

danbst

Okay, I've got a need to build Firefox from source, and I'd like to do that on a remote machine, and then copy build result back to my laptop. With Nix, using bastion host. I'll note details of my successful adventure.

Setup & Sources of knowledge

Here's the list of resources I've used actively:

• https://nixos.wiki/wiki/Distributed_build
• https://nixos.org/nix/manual/#conf-trusted-substituters and various other configuration parameters
• https://github.com/NixOS/nixpkgs/blob/release-19.09/nixos/modules/services/misc/nix-daemon.nix which contains mappings from Nix config names to NixOS config names (damn, they are different!)

Here's my setup:

nmattia

# MIT License, see below
#
# These are some helpers for figuring out the derivations attributes of runtime
# dependencies of a derivation, in particular the function `runtimeReport`. At
# the bottom of the file you can see it used on `hello`. Spoiler: glibc is a
# runtime dependency.
# For more info see
#
#   https://nmattia.com/posts/2019-10-08-runtime-dependencies.html

rpigott

#compdef swaymsg

typeset -A opt_args
__swaymsg() {
	# Reuse socket path from command line if present
	swaymsg ${(kv)opt_args[(I)-s|--socket]} "$@" 2>/dev/null
}

# _sway
# sway ipc {{{