Oleg Shparber trollixx

Options built-in, by default, to most Qt-based applications.

QApplication

https://doc.qt.io/qt-5/qapplication.html#QApplication https://github.com/qt/qtbase/blob/dev/src/widgets/kernel/qapplication.cpp#L449

-qdevel (obsolete)
--qmljsdebugger

Commit Message Guidelines

In the last few years, the number of programmers concerned about writing structured commit messages have dramatically grown. As exposed by Tim Pope in article readable commit messages are easy to follow when looking through the project history. Moreover the AngularJS contributing guides introduced conventions that can be used by automation tools to automatically generate useful documentation, or by developers during debugging process.

This document borrows some concepts, conventions and even text mainly from these two sources, extending them in order to provide a sensible guideline for writing commit messages.

Goals
Proposal
- Commit Message Format

Allowed ``

Improve Fonts

Newest

Make your Arch fonts beautiful easily! This is what I do when I install Arch Linux to improve the fonts.

You may consider the following settings to improve your fonts for system-wide usage without installing a patched font library packages (eg. Infinality):

Install some fonts, for example:
sudo pacman -S ttf-dejavu ttf-liberation noto-fonts

Git DMZ Flow

I've been asked a few times over the last few months to put together a full write-up of the Git workflow we use at RichRelevance (and at Precog before), since I have referenced it in passing quite a few times in tweets and in person. The workflow is appreciably different from GitFlow and its derivatives, and thus it brings with it a different set of tradeoffs and optimizations. To that end, it would probably be helpful to go over exactly what workflow benefits I find to be beneficial or even necessary.

Two developers working on independent features must never be blocked by each other
- No code freeze! Ever! For any reason!
A developer must be able to base derivative work on another developer's work, without waiting for any third party
Two developers working on inter-dependent features (or even the same feature) must be able to do so without interference from (or interfering with) any other parties
Developers must be able to work on multiple features simultaneously, or at lea

Commit Message Conventions

These rules are adopted from the AngularJS commit conventions.

Goals
Generating CHANGELOG.md
- Recognizing unimportant commits
- Provide more information when browsing the history
Format of the commit message
Subject line

Initialize

gitflow	git
`git flow init`	`git init`
	`git commit --allow-empty -m "Initial commit"`
	`git checkout -b develop master`

	# This isn't meant to be a fully featured implementation. It's just a small playground project.
	# Use `cmake -Bbuild -S. -GNinja` to generate the project
	# Then use `cmake --build build --target package` to generate a .appimage file ready to go
	# This project DOES do dangerous things and tries to download the linuxdeploy tool directly.
	# When this makes it into IXM, it will be expected that users have the linuxdeploy tool installed to some location.
	# It will NOT download and execute something from the internet.
	cmake_minimum_required(VERSION 3.16)
	project(summon-test LANGUAGES CXX VERSION 0.1.0)

	add_executable(app)

	# References:
	# https://cmake.org/cmake/help/latest/command/add_custom_target.html
	# https://samthursfield.wordpress.com/2015/11/21/cmake-dependencies-between-targets-and-files-and-custom-commands/
	# https://gist.github.com/socantre/7ee63133a0a3a08f3990
	# https://stackoverflow.com/questions/24163778/how-to-add-custom-target-that-depends-on-make-install
	# https://stackoverflow.com/questions/30719275/add-custom-command-is-not-generating-a-target
	# https://stackoverflow.com/questions/26024235/how-to-call-a-cmake-function-from-add-custom-target-command
	# https://blog.csdn.net/gubenpeiyuan/article/details/51096777

	cmake_minimum_required(VERSION 3.10)

	Windows Registry Editor Version 5.00

	[HKEY_CURRENT_USER\Console]
	"ColorTable00"=dword:00282828
	"ColorTable01"=dword:00888545
	"ColorTable02"=dword:001a9798
	"ColorTable03"=dword:006a9d68
	"ColorTable04"=dword:001d24cc
	"ColorTable05"=dword:008662b1
	"ColorTable06"=dword:002199d7

	// Qt
	#include <QCoreApplication>
	#include <QStringList>
	#include <QFile>
	#include <QHash>
	#include <QTextStream>
	#include <QtDebug>

	int main( int argc, char *argv[] )
	{