nemo iiey

THIS GIST WAS MOVED TO TERMSTANDARD/COLORS REPOSITORY.

PLEASE ASK YOUR QUESTIONS OR ADD ANY SUGGESTIONS AS A REPOSITORY ISSUES OR PULL REQUESTS INSTEAD!

Unix signals in Qt applications

It's quite easy to catch unix signals in Qt applications. you may like to ignore or accept them.

#include <QCoreApplication>

#include <initializer_list>
#include <signal.h>
#include <unistd.h>

In your local clone of your forked repository, you can add the original GitHub repository as a "remote". ("Remotes" are like nicknames for the URLs of repositories - origin is one, for example.) Then you can fetch all the branches from that upstream repository, and rebase your work to continue working on the upstream version. In terms of commands that might look like:

Add the remote, call it "upstream":

git remote add upstream https://github.com/whoever/whatever.git

Fetch all the branches of that remote into remote-tracking branches, such as upstream/master:

git fetch upstream

Creating your own ag.vim

Vim provides built-in mechanisms to search through projects in the form of the grep command. However, on large projects, grep is known to be slow; and hence people have been switching to simpler searchers like ack, and faster, parallel (metal?) searchers like ag and pt. Correspondingly, several plugins have been created that integrate these tools in vim: ack.vim, ag.vim, etc.

However, it's actually very easy to get the functionalities these plugins provide (faster search, results in quickfix-window, jumps, previews, and so on) in vanilla Vim itself; in fact, Vim already populates the grep-search results in a quickfix window. We just need to tell Vim to do the following things (use-case: ag):

Use ag as the default grep program
Open quickfix window by default
Create mappin

Managing plugins in Vim: The basics

Let's say the plugin is at a GitHub URL https://github.com/manasthakur/foo. First get the plugin by either cloning it (git clone https://github.com/manasthakur.foo.git) or simply downloading it as a zip (from its GitHub page).

Adding a plugin in Vim is equivalent to adding the plugin's code properly into its runtimepath (includes the $HOME/.vim directory by default). For example, if the layout of a plugin foo is as follows:

foo/autoload/foo.vim
foo/plugin/foo.vim

	#! /usr/bin/env python

	""" Convert values between RGB hex codes and xterm-256 color codes.

	Nice long listing of all 256 colors and their codes. Useful for
	developing console color themes, or even script output schemes.

	Resources:
	* http://en.wikipedia.org/wiki/8-bit_color
	* http://en.wikipedia.org/wiki/ANSI_escape_code

	#! /bin/bash

	# This program is just an example of how to make a whiptail menu and some basic commands.
	# Copyright (C) 2016 Baljit Singh Sarai

	# This program is free software; you can redistribute it and/or
	# modify it under the terms of the GNU General Public License
	# as published by the Free Software Foundation; either version 2
	# of the License.

	# GIT heart FZF
	# -------------

	is_in_git_repo() {
	git rev-parse HEAD > /dev/null 2>&1
	}

	fzf-down() {
	fzf --height 50% --min-height 20 --border --bind ctrl-/:toggle-preview "$@"
	}

	#!/bin/bash

	# Tom Hale, 2016. MIT Licence.
	# Print out 256 colours, with each number printed in its corresponding colour
	# See http://askubuntu.com/questions/821157/print-a-256-color-test-pattern-in-the-terminal/821163#821163

	set -eu # Fail on errors or undeclared variables

	printable_colours=256

	figlet "I've got something to say"

	figlet -f thick "Make Tech ASCIIer"

	date \| figlet -f basic