start new:
tmux
start new with session name:
tmux new -s myname
# ref: http://www.tfidf.com/ | |
# Example: | |
# Consider a document containing 100 words wherein the word cat appears 3 times. | |
# The term frequency (i.e., tf) for cat is then (3 / 100) = 0.03. Now, assume we | |
# have 10 million documents and the word cat appears in one thousand of these. | |
# Then, the inverse document frequency (i.e., idf) is calculated as log(10,000,000 / 1,000) = 4. | |
# Thus, the Tf-idf weight is the product of these quantities: 0.03 * 4 = 0.12. | |
# | |
# Hence: | |
# 1. Calculate term frequency |
This is a guide on how to send a properly formatted multipart email. Multipart email strings are MIME encoded, raw text email templates. This method of structuring an email allows for multiple versions of the same email to support different email clients.
// Example Multipart Email:
From: sender@example.com
To: recipient@example.com
Subject: Multipart Email Example
Content-Type: multipart/alternative; boundary="boundary-string"
$ git remote rm origin | |
$ git remote add origin git@github.com:aplikacjainfo/proj1.git | |
$ git config master.remote origin | |
$ git config master.merge refs/heads/master |
#include <QCommandLineParser> | |
#include <QCoreApplication> | |
#include <QTextStream> | |
int main(int argc, char *argv[]) | |
{ | |
QCoreApplication app(argc, argv); | |
QCommandLineParser parser; | |
parser.setOptionsAfterPositionalArgumentsMode(QCommandLineParser::ParseAsOptions); | |
parser.addPositionalArgument("subcommand", |
Git sees every file in your working copy as one of three things:
Ignored files are usually build artifacts and machine generated files that can be derived from your repository source or should otherwise not be committed. Some common examples are:
Ctrl + Alt + Space
curl -X POST -d '{"public":true,"files":{"test.txt":{"content":"String file contents"}}}' -u mgarciaisaia:mypassword https://api.github.com/gists | |
# https://stackoverflow.com/questions/34048241/how-to-create-a-gist-on-command-line |
I've got 2 flavors of launching VS Code on remote servers for you
Clean terminal, you know you want to launch code on a remote server. Check out sshcode.sh
You want to launch code on your local machine from inside an existing SSH session. This needs a bit of setup, but seems to work pretty well. Hacks inbound!
PermitLocalCommand yes
in your SSH config (see example)LocalCommand
to stash the username, IP, and current directory in a local file when you connecthack.sh
in your home directoryNow to connect, use the SSH escape sequence (default single tilde ~
) along with !command
to invoke the script