573

My guess: This site https://gitlab.com/pygotham/2017 is built by that expression: https://gist.github.com/dirn/04c9e134ab34dc76069d65e067086c3c

573

Got:

nixpkgs error: a 'x86_64-linux' with features {kvm} is required to build

https://github.com/NixOS/nix/issues/2964#issuecomment-504097120 hinted

Added accordingly to nano ~/.config/nix/nix.conf https://www.mankier.com/5/nix.conf

Works.

573

Keybase proof

I hereby claim:

• I am 573 on github.
• I am corocoton (https://keybase.io/corocoton) on keybase.
• I have a public key ASCNAckkEdWOueSXFAj50-kLtY5o2ejpwgZ36IuYYDAuPwo

To claim this, I am signing this object:

573

https://wiki.archlinux.org/index.php/PDF,_PS_and_DjVu#Viewers qpdfview: Duplex printing works, as well as filling forms.

573

http://archive.fo/bGQ18 (# cat ~/.asoundrc
defaults.pcm.card=1)
http://archive.fo/PueJd (under the headline The manual sink configuration method; also installed pavucontrol)
Basically there is no way around pulseaudio IMHO on that machine.

573

Solved graphics issues (nvidia-340) in Ubuntu once and forall with the following kind guide: http://archive.fo/w0tKN

573

Q: I cannot seem to run the examples listed i. e. here. How do they work?
A: First look after using the right modules: (use 'midje.repl) and also (require '[midje.checking.core :as checking]). The trick is then, each time a wiki page speaks of "checker" and lists examples of this concept to still wrap those example inside (fact ...) i. e. (fact "abc" => (contains "bc")). That's all there is to know.

573

http://archive.fo/cFcjS, to quote it:

Note the difference in plugins and dependencies:

$ lein update-in :dependencies conj '[midje "1.9.8"]' -- update-in :plugins conj '[lein-midje "3.2.1"]' -- repl

573

https://archive.fo/NMyaW#selection-16209.26-16209.79
Example:

curl -L -o ~/.ammonite/predef.sc https://git.io/vHaKQ

573

$ cd C:\Users\me\scoop\buckets\extras\bucket
$ git log --oneline | findstr -i c1456fd
### from here on you could use any chrome.json or even the scoop procedures for updating/testing versions etc.
$ git checkout c1456fd -- .\chrome.json
$ git status
On branch master
Your branch is up to date with 'origin/master'.

Changes to be committed:
  (use "git reset HEAD <file>..." to unstage)