You may want a linter plugin to lint your code in Vim but you probably don't need it. At least try the built-in way before jumping on the plugin bandwagon.
autocmd FileType <filetype> setlocal makeprg=<external command>
This autocommand tells Vim to use <external command> when invoking :make % in a <filetype> buffer. You can add as many similar lines as needed for other languages.
For this configuration you can use web server you like, i decided, because i work mostly with it to use nginx.
Generally, properly configured nginx can handle up to 400K to 500K requests per second (clustered), most what i saw is 50K to 80K (non-clustered) requests per second and 30% CPU load, course, this was 2 x Intel Xeon with HyperThreading enabled, but it can work without problem on slower machines.
You must understand that this config is used in testing environment and not in production so you will need to find a way to implement most of those features best possible for your servers.
| #!/usr/bin/env bash | |
| # Time-stamp: <2017-04-27 09:57:21 kmodi> | |
| # Time-stamp: <2018-03-20 12:58:02 bobpaul> | |
| # derived from kmodi's gist: https://gist.github.com/kaushalmodi/74e9875d5ab0a2bc1010447f1bee5d0a | |
| # | |
| # Example of using getopt to parse command line options | |
| # http://stackoverflow.com/a/29754866/1219634 Limitation: All the options | |
| # starting with - have to be listed in --options/--longoptions, else getopt will | |
| # error out. | |
| # The downside is that if you intend to use this as a wrapper to some other program, |
| # Bash best practices and style-guide | |
| Just simple methods to keep the code clean. | |
| Inspired by [progrium/bashstyle](https://github.com/progrium/bashstyle) and [Kfir Lavi post](http://www.kfirlavi.com/blog/2012/11/14/defensive-bash-programming/). | |
| ## Quick big rules | |
| * All code goes in a function | |
| * Always double quote variables |
Here is an essay version of my class notes from Class 1 of CS183: Startup. Errors and omissions are my own. Credit for good stuff is Peter’s entirely.
CS183: Startup—Notes Essay—The Challenge of the Future
Purpose and Preamble
| { | |
| /* ~/Library/KeyBindings/DefaultKeyBinding.dict | |
| See https://gist.github.com/zsimic/1367779, prefix cheatsheet: | |
| Char Short Key | |
| $ S- Shift ⇧ | |
| ^ C- CTRL ⌃ | |
| ~ O- Option ⌥ (⊞ Win key position on PC) | |
| @ M- Command ⌘ (Alt position on PC) | |
| # Numeric Keypad |
The always enthusiastic and knowledgeable mr. @jasaltvik shared with our team an article on writing (good) Git commit messages: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the
| abandoned | |
| able | |
| absolute | |
| adorable | |
| adventurous | |
| academic | |
| acceptable | |
| acclaimed | |
| accomplished | |
| accurate |
| #!/bin/bash | |
| # | |
| # PostgreSQL Backup Script Ver 1.0 | |
| # http://autopgsqlbackup.frozenpc.net | |
| # Copyright (c) 2005 Aaron Axelsen <axelseaa@amadmax.com> | |
| # | |
| # This script is based of the AutoMySQLBackup Script Ver 2.2 | |
| # It can be found at http://sourceforge.net/projects/automysqlbackup/ | |
| # | |
| # The PostgreSQL changes are based on a patch agaisnt AutoMySQLBackup 1.9 |