This serves as a quick reference and showcase of GitHub Flavored Markdown. For more complete info, see John Gruber's original spec and the Github-flavored Markdown info page.
This is a guide to Vim Script development for Python developers. Sample code for the various expressions, statements, functions and programming constructs is shown in both Python and Vim Script. This is not intended to be a tutorial for developing Vim scripts. It is assumed that the reader is familiar with Python programming.
For an introduction to Vim Script development, refer to usr_41.txt, eval.txt and Learn Vimscript the Hard Way
For a guide similar to this one for JavaScript developers, refer to Vim Script for the JavaScripter
This guide only describes the programming constructs that are present in both Python and Vim. The constructs that are unique to Vim (e.g. autocommands, [key-mapping](https://vimhelp.org/map.txt.html#key-m
Hello software developers,
Please check your code to ensure you're not making one of the following mistakes related to cryptography.
- Writing your own home-grown cryptography primitives (For example: Mifare Classic)
- Exception: For the sake of learning, but don't deploy it in production.
- Using a fast hash function (e.g. MD5, SHA256) for storing passwords. Use bcrypt instead.
- Not using a cryptographically secure random number generator
- Log into the container and create an empty directory, this will be the mount point
- Log out and stop the container.
- Open to your container's config file
- For regular LXC containers:
/var/lib/lxc/mycontainer/config - For unprivileged LXC containers:
$HOME/.local/share/lxc/mycontainer/config
- For regular LXC containers:
- Add a new line above the
lxc.mountdirective, that follows the format below. Substitute proper paths as necessary:lxc.mount.entry = /path/to/folder/on/host /path/to/mount/point none bind 0 0
- Both of these paths are relative to the host machine.
| # Hello, and welcome to makefile basics. | |
| # | |
| # You will learn why `make` is so great, and why, despite its "weird" syntax, | |
| # it is actually a highly expressive, efficient, and powerful way to build | |
| # programs. | |
| # | |
| # Once you're done here, go to | |
| # http://www.gnu.org/software/make/manual/make.html | |
| # to learn SOOOO much more. |
| from django.contrib import admin, messages | |
| from django.http import HttpResponseRedirect | |
| from django.shortcuts import render | |
| from my_app.forms import CustomForm | |
| class FakeModel(object): | |
| class _meta: | |
| app_label = 'my_app' # This is the app that the form will exist under |
| simple and clear algorithm description: | |
| http://www.titouangalopin.com/blog/articles/2014/05/simhash-or-the-way-to-compare-quickly-two-datasets | |
| a python impl | |
| http://liangsun.org/posts/a-python-implementation-of-simhash-algorithm/ | |
| original paper of simhash | |
| http://www.cs.princeton.edu/courses/archive/spr04/cos598B/bib/CharikarEstim.pdf | |
| simhash impl doc |
| #!/bin/bash | |
| # | |
| # DESCRIPTION: | |
| # | |
| # Set the bash prompt according to: | |
| # * the active virtualenv | |
| # * the branch of the current git/mercurial repository | |
| # * the return value of the previous command | |
| # * the fact you just came from Windows and are used to having newlines in | |
| # your prompts. |
| function parse_git_branch_name { | |
| git rev-parse --abbrev-ref HEAD | |
| } | |
| function parse_git_description { | |
| git config branch.$(parse_git_branch_name).description | |
| } | |
| alias gs='echo $(parse_git_branch_name): $(parse_git_description) && git status' |