Tristano Ajmone tajmone

## gist:7360908

      
              1 file
            
          
              3641 forks
            
          
              1011 comments
            
          
              16629 stars
            
          
                rxaviers
                / gist:7360908
            
            
              Last active
              May 9, 2024 15:35
            
              
                Complete list of github markdown emoji markup
              
          
    People


 :bowtie:
😄 :smile:
😆 :laughing:


😊 :blush:
😃 :smiley:
☺️ :relaxed:


😏 :smirk:
😍 :heart_eyes:
😘 :kissing_heart:


😚 :kissing_closed_eyes:
😳 :flushed:
😌 :relieved:


😆 :satisfied:
😁 :grin:
😉 :wink:


😜 :stuck_out_tongue_winking_eye:
😝 :stuck_out_tongue_closed_eyes:
😀 :grinning:


😗 :kissing:
😙 :kissing_smiling_eyes:
😛 :stuck_out_tongue:


## GitHub Flavored Asciidoc (GFA).adoc

      
              1 file
            
          
              33 forks
            
          
              50 comments
            
          
              259 stars
            
          
                dcode
                / GitHub Flavored Asciidoc (GFA).adoc
            
            
              Last active
              May 9, 2024 06:11
            
              
                Demo of some useful tips for using Asciidoc on GitHub
              
          
    GitHub Flavored Asciidoc (GFA)


## meta-tags.md

      
              1 file
            
          
              462 forks
            
          
              75 comments
            
          
              1411 stars
            
          
                lancejpollard
                / meta-tags.md
            
            
              Created
              March 5, 2012 13:54
            
              
                Complete List of HTML Meta Tags
              
          
    Copied from http://code.lancepollard.com/complete-list-of-html-meta-tags/
Basic HTML Meta Tags

<meta name="keywords" content="your, tags"/>
<meta name="description" content="150 words"/>
<meta name="subject" content="your website's subject">
<meta name="copyright"content="company name">
<meta name="language" content="ES">

  
## regular_expression_engine_comparison.md

      
              1 file
            
          
              32 forks
            
          
              15 comments
            
          
              196 stars
            
          
                CMCDragonkai
                / regular_expression_engine_comparison.md
            
            
              Last active
              May 4, 2024 16:50
            
              
                Regular Expression Engine Comparison Chart
              
          
    Regular Expression Engine Comparison Chart

Many different applications claim to support regular expressions. But what does
that even mean?
Well there are lots of different regular expression engines, and they all have
different feature sets and different time-space efficiencies.
The information here is just copied from: http://regular-expressions.mobi/refflavors.html

  
## GitHub-Forking.md

      
              1 file
            
          
              778 forks
            
          
              110 comments
            
          
              2872 stars
            
          
                Chaser324
                / GitHub-Forking.md
            
            
              Last active
              May 2, 2024 05:49
            
              
                GitHub Standard Fork & Pull Request Workflow
              
          
    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.
Creating a Fork

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

  
## metatags.html
<html>
  <head>

    <!--Recommended Meta Tags-->
    <meta charset="utf-8">
    <meta name="language" content="english">
    <meta http-equiv="content-type" content="text/html">
    <meta name="author" content=”Rafayel Mkrtchyan”>
    <meta name="designer" content=”Rafayel Mkrtchyan”>
    <meta name="publisher" content=”Rafayel Mkrtchyan”>

## comparing-git-add-all.md

      
              1 file
            
          
              8 forks
            
          
              34 comments
            
          
              63 stars
            
          
                dsernst
                / comparing-git-add-all.md
            
            
              Last active
              January 25, 2024 17:00
            
              
                Compare `git add .` vs `git add -A`
              
          
    git add . vs git add -A

Both of these will stage all files, including new files (which git commit -a misses) and deleted files.
The difference is that git add -A also stages files in higher directories that still belong to the same git repository. Here's an example:
/my-repo
  .git/
 subfolder/


## create-custom-css.bash
#!/usr/bin/env bash

usage() {
    cat << HEREDOC 1>&2
Usage: create-custom-css.bash [OPTION]

  -d, --debug enable debug mode
  -h, --help  display this help and exit
HEREDOC
    exit 1

## include.asciidoc.txt
== Included Section

Look, I came from out of the [blue]#blue#!

--
I'm keepin' it open.

An 'open block', like this one, can contain other blocks.

It can also act as any other block. (TODO)

## crayola.json
[
    {
        "hex": "#EFDECD",
        "name": "Almond",
        "rgb": "(239, 222, 205)"
    },
    {
        "hex": "#CD9575",
        "name": "Antique Brass",
        "rgb": "(205, 149, 117)"
`:bowtie:`	😄 `:smile:`	😆 `:laughing:`
😊 `:blush:`	😃 `:smiley:`	☺️ `:relaxed:`
😏 `:smirk:`	😍 `:heart_eyes:`	😘 `:kissing_heart:`
😚 `:kissing_closed_eyes:`	😳 `:flushed:`	😌 `:relieved:`
😆 `:satisfied:`	😁 `:grin:`	😉 `:wink:`
😜 `:stuck_out_tongue_winking_eye:`	😝 `:stuck_out_tongue_closed_eyes:`	😀 `:grinning:`
😗 `:kissing:`	😙 `:kissing_smiling_eyes:`	😛 `:stuck_out_tongue:`
	<html>
	<head>

	<!--Recommended Meta Tags-->
	<meta charset="utf-8">
	<meta name="language" content="english">
	<meta http-equiv="content-type" content="text/html">
	<meta name="author" content=”Rafayel Mkrtchyan”>
	<meta name="designer" content=”Rafayel Mkrtchyan”>
	<meta name="publisher" content=”Rafayel Mkrtchyan”>
	#!/usr/bin/env bash

	usage() {
	cat << HEREDOC 1>&2
	Usage: create-custom-css.bash [OPTION]

	-d, --debug enable debug mode
	-h, --help display this help and exit
	HEREDOC
	exit 1
	== Included Section

	Look, I came from out of the [blue]#blue#!

	--
	I'm keepin' it open.

	An 'open block', like this one, can contain other blocks.

	It can also act as any other block. (TODO)
	[
	{
	"hex": "#EFDECD",
	"name": "Almond",
	"rgb": "(239, 222, 205)"
	},
	{
	"hex": "#CD9575",
	"name": "Antique Brass",
	"rgb": "(205, 149, 117)"