wraithmonster

################################################################################
# Command line processing
################################################################################

# Parse the command line arguments. 
while [ "$#" -gt "0" ]; do
    case "$1" in
     
    #   TODO:    Create some script options. 
    #   EXAMPLE: Uncomment below to assign a 'destination directory', DST_DIR, 

unix-junkie

#include <stdio.h>

#include <Xm/Xm.h>
#include <Xm/MwmUtil.h>
#include <Xm/AtomMgr.h>
#include <Xm/PushB.h>
#include <Xm/Protocols.h>

Widget topLevel;

dbapl

*.ods diff=odf
*.odt diff=odf
*.odp diff=odf
*.pdf diff=pdf
*.PDF diff=pdf
*.apk diff=apk
*.bz2 diff=bz2
*.gz  diff=gzip
*.zip diff=zip
*.tar diff=tar

brettz9

[user]
	name = Brett Zamir
	email = brettz9@yahoo.com
[gui]
[gui]
	encoding = utf-8
	recentrepo = C:/wamp/www/_servers/me-pedia.org/me-pedia.org/extensions/intersection
	recentrepo = C:/wamp/www/json-schema-spec
	recentrepo = C:/wamp/www/file-type-icons
	recentrepo = C:/wamp/www/symbols-tree-view

steinwaywhw

• Use curl to get the JSON response for the latest release
• Use grep to find the line containing file URL
• Use cut and tr to extract the URL
• Use wget to download it

curl -s https://api.github.com/repos/jgm/pandoc/releases/latest \
| grep "browser_download_url.*deb" \
| cut -d : -f 2,3 \
| tr -d \" \

shiveshabhishek

The NERDTree is a file system explorer for the Vim editor. Using this plugin, users can visually browse complex directory hierarchies, quickly open files for reading or editing, and perform basic file system operations.

To install NERDTree

1. Go to : https://github.com/scrooloose/nerdtree
2. Clone the repo git clone https://github.com/scrooloose/nerdtree.git
3. Create a directory , mkdir ~/.vim
4. Move the contents of the repo to the new directory created mv /path/to/nerdtree-master/* ~/.vim/
5. Now, open any file with vim and, first press Esc and then type : :NERDTree and you are done!
6. To go out of NERDTree, press Esc and type q

gtors

Guillaume Papin(@Sarcasm) has a thorough article about compilation databases.

CMake

% mkdir build
% (cd build; cmake -DCMAKE_EXPORT_COMPILE_COMMANDS=YES ..)
% ln -s build/compile_commands.json

benasher44

# Escape XML characters
s/&/\&/g
s/"/\"/g
s/'/\'/g
s/</\&lt;/g
s/>/\&gt;/g

s/\[==========\] Running ([0-9]+) tests from [0-9]+ test cases./<testsuites><testsuite tests="\1">/g
s/\[ RUN      \] ([[:alnum:]_-]+)\.(.+)/<testcase classname="\1" name="\2">/g
s/\[----------\].+//g

ajkaanbal

#
# SIXEL color graphics DEMO
#
# xterm pl#301 with --enable-sixel-graphics option
# gnuplot with --with-bitmap-terminals option
#
# Now the color palette of xterm VT-340 mode is limited to 16.
# If you want to change it to 256, apply the following patch.
# https://gist.github.com/saitoha/7822989/raw/20727b88f0f826bfcb9d644907944b29a456b67f/graphics.c.diff
#

t27

Dealing with the Linux OOM Killer at the program level

Do this in cases when you dont want to change the os-level settings, but only want to disable the OOM killer for a single process. This is useful when youre on a shared machine/server.

The OOM killer uses the process level metric called oom_score_adj to decide if/when to kill a process. This file is present in /proc/$pid/oom_score_adj. The oom_score_adj can vary from -1000 to 1000, by default it is 0.

You can add a large negative score to this file to reduce the probability of your process getting picked and terminated by OOM killer. When you set it to -1000, it can use 100% memory and still avoid getting terminated by OOM killer.