As configured in my dotfiles.
start new:
tmux
start new with session name:
#!/usr/bin/env ruby -wKU | |
require "rubygems" | |
require "appscript" | |
include Appscript | |
chrome = app("Google Chrome") | |
safari = app("Safari") | |
chrome_tab = chrome.windows[1].active_tab |
As configured in my dotfiles.
start new:
tmux
start new with session name:
#!comment: This is a list of the top 100,000 most frequently-used English words | |
#!comment: according to Wiktionary. | |
#!comment: | |
#!comment: It was compiled in August 2005 and coalesced into a handy list for | |
#!comment: use in John the Ripper. | |
#!comment: | |
#!comment: | |
#!comment: Pull date: Sun Jan 15 22:03:54 2012 GMT | |
#!comment: | |
#!comment: Sources: |
To run this, you can try:
curl -ksO https://gist.githubusercontent.com/nicerobot/2697848/raw/uninstall-node.sh
chmod +x ./uninstall-node.sh
./uninstall-node.sh
rm uninstall-node.sh
This means, on your local machine, you haven't made any SSH keys. Not to worry. Here's how to fix:
*nix
based command prompt (but not the default Windows Command Prompt!)cd ~/.ssh
. This will take you to the root directory for Git (Likely C:\Users\[YOUR-USER-NAME]\.ssh\
on Windows).ssh
folder, there should be these two files: id_rsa
and id_rsa.pub
. These are the files that tell your computer how to communicate with GitHub, BitBucket, or any other Git based service. Type ls
to see a directory listing. If those two files don't show up, proceed to the next step. NOTE: Your SSH keys must be named id_rsa
and id_rsa.pub
in order for Git, GitHub, and BitBucket to recognize them by default.ssh-keygen -t rsa -C "your_email@example.com"
. Th// | |
// loads remote file using fetch() streams and "pipe" it to webaudio API | |
// remote file must have CORS enabled if on another domain | |
// | |
// mostly from http://stackoverflow.com/questions/20475982/choppy-inaudible-playback-with-chunked-audio-through-web-audio-api | |
// | |
function play(url) { | |
var context = new (window.AudioContext || window.webkitAudioContext)(); |
"""A generic module to read data.""" | |
import numpy | |
import collections | |
from tensorflow.python.framework import dtypes | |
class DataSet(object): | |
"""Dataset class object.""" | |
def __init__(self, |
import torch | |
import torchvision | |
import torch.nn as nn | |
import torch.nn.functional as F | |
import torchvision.transforms as transforms | |
import matplotlib.pyplot as plt | |
import numpy as np | |
import torch.optim as optim | |
from torch.autograd import Variable |
Hi All! | |
I've recently launched a tool that wraps many of the commands here with a user interface. This desktop application is currently available for macOS. There's a roadmap outlining planned features for the near future. | |
Feel free to request any features you'd like to see, and I'll prioritize them accordingly. | |
One of the most important aspects of this application is that every command executed behind the scenes is displayed in a special log section. This allows you to see exactly what’s happening and learn from it. | |
Here's the link to the repository: https://github.com/Pulimet/ADBugger | |
App Description: | |
ADBugger is a desktop tool designed for debugging and QA of Android devices and emulators. It simplifies testing, debugging, and performance analysis by offering device management, automated testing, log analysis, and remote control capabilities. This ensures smooth app performance across various setups. |