matthewjberger

#!/bin/sh

echo "Install neovim from ppa"
sudo add-apt-repository -y ppa:neovim-ppa/unstable
sudo apt-get update
sudo apt-get install -y neovim

echo "Compile and install neovim-qt"
git clone https://github.com/maorv/neovim-qt.git
cd neovim-qt && mkdir build && cd build

matthewjberger

// Sample file using the Google C++ coding standard.
//
// http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml
//
// General rules:
//   - Indents are two spaces. No tabs should be used anywhere.
//   - Each line must be at most 80 characters long.
//   - Comments can be // or /* but // is most commonly used.
//   - File names should be lower_case.c or lower-case.c
//

matthewjberger

#Create blank branch
git symbolic-ref HEAD refs/heads/gh-pages
rm .git/index
git clean -fdx
touch .gitignore
git add .gitignore
git commit -m "Initial Commit"

#Push to origin
git push origin gh-pages

matthewjberger

#!/bin/bash

gconftool-2 -s -t string /apps/guake/style/font/palette "#3F3F3F3F3F3F:#CCCC93939393:#7F7F9F9F7F7F:#E3E3CECEABAB:#DFDFAFAF8F8F:#CCCC93939393:#8C8CD0D0D3D3:#DCDCDCDCCCCC:#3F3F3F3F3F3F:#CCCC93939393:#7F7F9F9F7F7F:#E3E3CECEABAB:#DFDFAFAF8F8F:#CCCC93939393:#8C8CD0D0D3D3:#DCDCDCDCCCCC"
gconftool-2 -s -t string /apps/guake/style/font/color "#ffffffffffff"
gconftool-2 -s -t string /apps/guake/style/background/color "#2E2E34343636"

matthewjberger

#include <iostream>
#include <map>
using namespace std;


class BaseClass{ 
public:
    virtual int funk() {
        return 0;
    }

matthewjberger

#include <iostream>
#include <map>
using namespace std;


class BaseClass{ 
public:
    virtual int funk() {
        return 0;
    }

matthewjberger

If you have a huge repository (in size and in history) and want to add a subfolder 
to your project as a submodule you can follow this example to save time and space
using git's shallow clone and shallow checkout feature. It is a bit more complicated
in this example because I assume that you want your submodule to track a non-default
branch, called `mybranch`, instead of the `master` branch. Things could probably get
a lot simpler when using the default branch. After following the commands in these
examples you can use `git submodule update` and `git submodule update --remote` as normal.

matthewjberger

#!/bin/bash

# Credits to:
#  - http://vstone.eu/reducing-vagrant-box-size/
#  - https://github.com/mitchellh/vagrant/issues/343

apt -y purge ri
apt -y purge installation-report landscape-common wireless-tools wpasupplicant ubuntu-serverguide
apt -y purge python-dbus libnl1 python-smartpm python-twisted-core libiw30
apt -y purge python-twisted-bin libdbus-glib-1-2 python-pexpect python-pycurl python-serial python-gobject python-pam python-openssl libffi5

matthewjberger

Table of Contents

• 1. Setup Cpp/C Development Environment in Spacemacs
  • 1.1. 1. Add c/c++ layer
    • 1.1.1. Notes

matthewjberger

No Box<T>

tl;dr: Avoid Box<T> in general.

Actually, this rule is so important that the Rust Pointer Guide explicitly says the same. Therefore without a further ado, you should avoid Box<T> except for these three cases:

1. When you absolutely need a trait object (Box<Trait>). But review carefully to see if it is indeed absolutely needed; you may try to generalize things too far, for example.

2. When you have a recursive data structure. This may be mandatory when you have an inherently recursive data (e.g. scene graph), but it may also be a sign of the premature optimization. Again, review carefully to see if you need to write a separate data structure yourself, and use the collection crate if possible.