(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
| (defun company-eshell-history (command &optional arg &rest ignored) | |
| (interactive (list 'interactive)) | |
| (cl-case command | |
| (interactive (company-begin-backend 'company-eshell-history)) | |
| (prefix (and (eq major-mode 'eshell-mode) | |
| (let ((word (company-grab-word))) | |
| (save-excursion | |
| (eshell-bol) | |
| (and (looking-at-p (s-concat word "$")) word))))) | |
| (candidates (remove-duplicates |
| /* | |
| * Random-Number Utilities (randutil) | |
| * Addresses common issues with C++11 random number generation. | |
| * Makes good seeding easier, and makes using RNGs easy while retaining | |
| * all the power. | |
| * | |
| * The MIT License (MIT) | |
| * | |
| * Copyright (c) 2015-2022 Melissa E. O'Neill | |
| * |
| // | |
| // echo_server.cpp | |
| // ~~~~~~~~~~~~~~~ | |
| // | |
| // Copyright (c) 2003-2014 Christopher M. Kohlhoff (chris at kohlhoff dot com) | |
| // Copyright (c) 2015 Andrew Hundt | |
| // | |
| // Distributed under the Boost Software License, Version 1.0. (See accompanying | |
| // file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) | |
| // |
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
| #define BOOST_TEST_MODULE subcommand options | |
| #include <boost/test/unit_test.hpp> | |
| #include <boost/program_options.hpp> | |
| #include <boost/variant/variant.hpp> | |
| #include <boost/variant/get.hpp> | |
| struct GenericOptions { | |
| bool debug_; | |
| }; |
| \usepackage{listings} | |
| \usepackage{lstautogobble} % Fix relative indenting | |
| \usepackage{color} % Code coloring | |
| \usepackage{zi4} % Nice font | |
| \definecolor{bluekeywords}{rgb}{0.13, 0.13, 1} | |
| \definecolor{greencomments}{rgb}{0, 0.5, 0} | |
| \definecolor{redstrings}{rgb}{0.9, 0, 0} | |
| \definecolor{graynumbers}{rgb}{0.5, 0.5, 0.5} |
You don't have to delete your local branch.
Simply delete your remote tracking branch:
git branch -d -r origin/<remote branch name>
(This will not delete the branch on the remote repo!)
See "Having a hard time understanding git-fetch"
there's no such concept of local tracking branches, only remote tracking branches.
| #include <boost/bind.hpp> | |
| #include "EventBus.h" | |
| std::hash<std::string> Event::key; | |
| void EventBus::Init() | |
| { | |
| is_io_running = true; | |
| m_work.reset(new boost::asio::io_service::work(io_service)); |
When working with Git, there are two prevailing workflows are Git workflow and feature branches. IMHO, being more of a subscriber to continuous integration, I feel that the feature branch workflow is better suited, and the focus of this article.
If you are new to Git and Git-workflows, I suggest reading the atlassian.com Git Workflow article in addition to this as there is more detail there than presented here.
I admit, using Bash in the command line with the standard configuration leaves a bit to be desired when it comes to awareness of state. A tool that I suggest using follows these instructions on setting up GIT Bash autocompletion. This tool will assist you to better visualize the state of a branc
| lorenz: lorenz.cpp | |
| g++ -o $@ $^ -std=c++11 -O3 \ | |
| -I${HOME}/work/odeint-v2 \ | |
| -I${HOME}/work/opencl/compute/include/ \ | |
| -lOpenCL -lboost_system -lboost_timer |