| # A two-line colored Bash prompt (PS1) with Git branch and a line decoration | |
| # which adjusts automatically to the width of the terminal. | |
| # Recognizes and shows Git, SVN and Fossil branch/revision. | |
| # Screenshot: http://img194.imageshack.us/img194/2154/twolineprompt.png | |
| # Michal Kottman, 2012 | |
| RESET="\[\033[0m\]" | |
| RED="\[\033[0;31m\]" | |
| GREEN="\[\033[01;32m\]" | |
| BLUE="\[\033[01;34m\]" |
| #!flask/bin/python | |
| from flask import Flask, jsonify, abort, request, make_response, url_for | |
| from flask.ext.httpauth import HTTPBasicAuth | |
| app = Flask(__name__, static_url_path = "") | |
| auth = HTTPBasicAuth() | |
| @auth.get_password | |
| def get_password(username): | |
| if username == 'miguel': |
| #!/bin/zsh | |
| function popup() { | |
| # how long bar stays open | |
| duration=4 | |
| # color of bar | |
| bar_bg='#4265f4' | |
| # bar position |
I recently had to make myself comfortable on a Windows box, which meant installing VIM and python. And being at compiling VIM I compiled it with support for other interpreters as well.
I made a gvim74.exe installation file, like the one you get from http://www.vim.org/download.php, but with the newest batches and the interpreter versions of my choice.
Preparations
| " ------------------------------ | |
| " Name: vimrc for windows | |
| " Author: keelii | |
| " Email: [email protected] | |
| " ------------------------------ | |
| " Startup {{{ | |
| filetype indent plugin on | |
| augroup vimrcEx |
| #!/bin/sh | |
| # extend non-HiDPI external display on DP* above HiDPI internal display eDP* | |
| # see also https://wiki.archlinux.org/index.php/HiDPI | |
| # you may run into https://bugs.freedesktop.org/show_bug.cgi?id=39949 | |
| # https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/883319 | |
| EXT=`xrandr --current | sed 's/^\(.*\) connected.*$/\1/p;d' | grep -v ^eDP | head -n 1` | |
| INT=`xrandr --current | sed 's/^\(.*\) connected.*$/\1/p;d' | grep -v ^DP | head -n 1` | |
| ext_w=`xrandr | sed 's/^'"${EXT}"' [^0-9]* \([0-9]\+\)x.*$/\1/p;d'` |
| @echo off | |
| :: Path to Sublime Text installation dir. | |
| SET stPath=%~dp0sublime_text.exe | |
| SET stPathOnly=%~dp0 | |
| :: Key name for the registry entries. | |
| SET UserEntry=Sublime Text | |
| SET AdminEntry=Sublime Text As Admin | |
| :: Context menu texts. | |
| SET "UserMenuText=Open with Sublime(&-)" | |
| SET "AdminMenuText=Open with Sublime As Admin(&+)" |
| #!/usr/bin/env python3 | |
| # -*- coding: utf-8 -*- | |
| """ | |
| unzip3_gbk.py: Deal with zip files using encoding GB2312/GBK/GB18030 | |
| """ | |
| import os | |
| # import sys | |
| import argparse | |
| import zipfile |
I’ll assume you are on Linux or Mac OSX. For Windows, replace ~/.vim/ with $HOME\vimfiles\ and forward slashes with backward slashes.
Vim plugins can be single scripts or collections of specialized scripts that you are supposed to put in “standard” locations under your ~/.vim/ directory. Syntax scripts go into ~/.vim/syntax/, plugin scripts go into ~/.vim/plugin, documentation goes into ~/.vim/doc/ and so on. That design can lead to a messy config where it quickly becomes hard to manage your plugins.
This is not the place to explain the technicalities behind Pathogen but the basic concept is quite straightforward: each plugin lives in its own directory under ~/.vim/bundle/, where each directory simulates the standard structure of your ~/.vim/ directory.