(from: https://github.com/Shopify/liquid/wiki/liquid-for-designers)
There are two types of markup in Liquid: Output and Tag.
- Output markup (which may resolve to text) is surrounded by
using System; | |
using System.Diagnostics; | |
using System.Runtime.InteropServices; | |
using System.Text; | |
using System.Threading; | |
namespace Caio.Proiete.Utils | |
{ | |
public class SilentProcessRunner : IDisposable | |
{ |
using System; | |
using System.Collections.Generic; | |
using System.Net.Sockets; | |
using System.Net; | |
using System.IO; | |
using System.Threading; | |
using System.Windows.Forms; | |
using Westwind.Utilities; | |
namespace Westwind.WebConnection |
(from: https://github.com/Shopify/liquid/wiki/liquid-for-designers)
There are two types of markup in Liquid: Output and Tag.
{% assign m = page.date | date: "%-m" %} | |
{% capture month_name_pt %} | |
{% case m %} | |
{% when '1' %}Janeiro | |
{% when '2' %}Fevereiro | |
{% when '3' %}Março | |
{% when '4' %}Abril | |
{% when '5' %}Maio | |
{% when '6' %}Junho | |
{% when '7' %}Julho |
#!/usr/bin/env python3 | |
import datetime | |
import logging | |
import requests | |
# Well-known keyword arguments used by the logging system. | |
_well_known_logger_kwargs = [ | |
"extra", | |
"exc_info", |
#include <stdio.h> | |
#include <windows.h> | |
#include <tchar.h> | |
#include <strsafe.h> | |
#include <mscoree.h> | |
// In case the machine this is compiled on does not have the most recent platform SDK | |
// with these values defined, define them here | |
#ifndef SM_TABLETPC | |
#define SM_TABLETPC 86 |
/**** Requires PeHeaderReader to determine bitness: http://code.cheesydesign.com/?p=572 ****/ | |
using Microsoft.Win32; | |
using System; | |
using System.Collections.Generic; | |
using System.IO; | |
using System.Security.AccessControl; | |
/// <summary> | |
/// See: http://support.microsoft.com/kb/240794 |
// Credits: John Stewien | |
// From: http://code.cheesydesign.com/?p=572 | |
/* | |
Reading the Portable Executable (PE) header in C# | |
My job consists of writing fully custom applications for groups of people. The time pressure of these projects is quite high, so generally people start using the application while I’m still writing it, which means I write it modularly and add features as I go along. I also fix bugs as they are discovered. My clients are 2 tiered where expert users get a new build first, they test if for a while, and if they think it’s acceptable they then pass it on to others. | |
This method of distribution is quite ad-hoc so when a client rings me up and asks me to view their screen to look at something, it’s useful to know what build they are running. To facillitate this I print the link date in the main Window Title so I instantly have an idea about how old the version is that I am looking at. This date is calculated at run time. To do this requires reading in the Portable Executable (PE) header from th |
Any GitHub wiki can be cloned by appending wiki.git
to the repo url, so the clone url for
the repo https://myorg/myrepo/
is: git@github.com/myorg/myrepo.wiki.git
(for ssh) or https://github.com/my/myrepo.wiki.git
(for https).
You make edits, and commit and push your changes, like any normal repo.
You need to clone the wiki repo and edit it on your system.
Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.
In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.
Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j