dhclient is the Dynamic Host Configuration Protocol (DHCP) Client one would use to allow a client to connect to a DHCP server.
$ sudo nano /etc/rc.local
#!/bin/bash
dhclient
exit 0| $targDir = "C:\inetpub\websites\ADA*\"; | |
| $subDir = $(Get-ChildItem "$targDir"); | |
| foreach($sub in $subDir) { | |
| $files = $(Get-Childitem $sub -Filter app_offline*.htm); | |
| foreach($file in $files) { | |
| $oldname = $file.FullName; |
| function rfc3339(d) { | |
| function pad(n) { | |
| return n < 10 ? "0" + n : n; | |
| } | |
| function timezoneOffset(offset) { | |
| var sign; | |
| if (offset === 0) { | |
| return "Z"; |
dhclient is the Dynamic Host Configuration Protocol (DHCP) Client one would use to allow a client to connect to a DHCP server.
$ sudo nano /etc/rc.local
#!/bin/bash
dhclient
exit 0| cd ~ | |
| sudo apt-get install unzip zip | |
| # see https://developer.android.com/studio#command-tools for latest commandline-tools | |
| wget https://dl.google.com/android/repository/commandlinetools-linux-9123335_latest.zip | |
| unzip commandlinetools-linux-6858069_latest.zip -d Android | |
| rm commandlinetools-linux-6858069_latest.zip | |
| sudo apt-get install -y lib32z1 openjdk-8-jdk # or install openjdk-11-jdk | |
| export JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64 | |
| export PATH=$PATH:$JAVA_HOME/bin | |
| printf "\n\nexport JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64\nexport PATH=\$PATH:\$JAVA_HOME/bin" >> ~/.bashrc |
Remap systemwide Caps + HJKL to arrow keys for Ubuntu 18.04 LTS (Bionic Beaver).
In file /usr/share/X11/xkb/symbols/us append in xkb_symbols "basic" scope before the closing bracket:
//hjkl
key <AC06> { [ h, H, Left ] };
key <AC07> { [ j, J, Down ] };
key <AC08> { [ k, K, Up ] };
key <AC09> { [ l, L, Right ] };
key { [ ISO_Level3_Shift ] }; This gist had a far larger impact than I imagined it would, and apparently people are still finding it, so a quick update:
(async main(){...}()) as a substitute for TLA. This completely eliminates the blocking problem (yay!) but it's less powerful, and harder to statically analyse (boo). In other words the lack of TLA is causing real problemsI'll leave the rest of this document unedited, for archaeological
Install, build and debug a react native app in WSL2 (Windows Subsystem for Linux) and Ubuntu.
| type CamelCase<S extends string> = S extends `${infer P1}_${infer P2}${infer P3}` | |
| ? `${Lowercase<P1>}${Uppercase<P2>}${CamelCase<P3>}` | |
| : Lowercase<S> | |
| type KeysToCamelCase<T> = { | |
| [K in keyof T as CamelCase<string & K>]: T[K] | |
| } | |
| type CamelToSnakeCase<S extends string> = S extends `${infer T}${infer U}` ? |
| #!/usr/bin/env python | |
| # | |
| # Based on a script by Donald Feury | |
| # https://gitlab.com/dak425/scripts/-/blob/master/trim_silenceV2 | |
| # https://youtu.be/ak52RXKfDw8 | |
| import math | |
| import sys | |
| import subprocess | |
| import os |
It's quite common to open up a pull request on GitHub and be confronted with the message This branch has conflicts that must be resolved. This situation arises when you create a feature branch on an older commit from the master branch. Maybe you forgot to run git pull master before git checkout -b geocoding_vignette or maybe a collaborator changed some of the same files on GitHub while you've been working on new things. There are many ways to fix this. One is using the Web Editor build into GitHub and fixing conflicts by hand. This works great if there are not too many conflicts.
Another technique is to rebase your pull request onto the master branch (Move your additional commits on top of the most recent master commit). This is conceptually clean, but sometimes confusing in practice to do cleanly. This example walks through the process where you want to do a rebase, and resolve conflicts by overwriting whatever is on the master branch with change