Rendra rendrap

## .gitconfig
[user]
	name = Pavan Kumar Sunkara
	email = pavan.sss1991@gmail.com
[core]
	editor = vim
	whitespace = fix,-indent-with-non-tab,trailing-space,cr-at-eol
	excludesfile = ~/.gitignore
[sendemail]
	smtpencryption = tls
	smtpserver = smtp.gmail.com

## jekyll-and-liquid.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                rendrap
                / jekyll-and-liquid.md
            
            
              Created
              September 28, 2017 10:26
                — forked from magicznyleszek/jekyll-and-liquid.md
            
              
                Jekyll & Liquid Cheatsheet
              
          
    Jekyll & Liquid Cheatsheet

A list of the most common functionalities in Jekyll (Liquid). You can use Jekyll with GitHub Pages, just make sure you are using the proper version.
Running

Running a local server for testing purposes:


## index.html
<html>
<head>
  <meta charset="UTF-8">
  <title>Bootstrap 3 Essential</title>
  <meta http-equiv="X-UA-Compatible" content="IE=edge">
  <meta name="viewport" content="width=device-width, initial-scale=1">
  <link rel="stylesheet" href="css/bootstrap.min.css">
  <link rel="stylesheet" type="text/css" href="css/styles.css">


## validate multiple AMP html file.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                rendrap
                / validate multiple AMP html file.md
            
            
              Last active
              February 13, 2018 09:10
            
              
                Validate multiple AMP html file using amphtml-validator
              
          
    Validate AMP html in current folder and subfolder

Tested on windows machine,
This is just some quick way to validate multiple AMP html using amphtml-validator
Dependency:


amphtml-validator
run npm install -g amphtml-validator to install globally


ruby


## publickey-git-error.markdown

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                rendrap
                / publickey-git-error.markdown
            
            
              Created
              April 11, 2018 07:09
                — forked from adamjohnson/publickey-git-error.markdown
            
              
                Fix "Permission denied (publickey)" error when pushing with Git
              
          
    "Help, I keep getting a 'Permission Denied (publickey)' error when I push!"

This means, on your local machine, you haven't made any SSH keys. Not to worry. Here's how to fix:

Open git bash (Use the Windows search. To find it, type "git bash") or the Mac Terminal. Pro Tip: You can use any *nix based command prompt (but not the default Windows Command Prompt!)
Type cd ~/.ssh. This will take you to the root directory for Git (Likely C:\Users\[YOUR-USER-NAME]\.ssh\ on Windows)
Within the .ssh folder, there should be these two files: id_rsa and id_rsa.pub. These are the files that tell your computer how to communicate with GitHub, BitBucket, or any other Git based service. Type ls to see a directory listing. If those two files don't show up, proceed to the next step. NOTE: Your SSH keys must be named id_rsa and id_rsa.pub in order for Git, GitHub, and BitBucket to recognize them by default.
To create the SSH keys, type ssh-keygen -t rsa -C "your_email@example.com". Th


## GitHub-Forking.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                rendrap
                / GitHub-Forking.md
            
            
              Created
              July 31, 2018 06:12
                — forked from Chaser324/GitHub-Forking.md
            
              
                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

  
## grok_vi.mdown

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                rendrap
                / grok_vi.mdown
            
            
              Created
              March 4, 2019 14:12
                — forked from nifl/grok_vi.mdown
            
              
                Your problem with Vim is that you don't grok vi.
              
          
    Answer by Jim Dennis on Stack Overflow question http://stackoverflow.com/questions/1218390/what-is-your-most-productive-shortcut-with-vim/1220118#1220118
Your problem with Vim is that you don't grok vi.
You mention cutting with yy and complain that you almost never want to cut whole lines. In fact programmers, editing source code, very often want to work on whole lines, ranges of lines and blocks of code. However, yy is only one of many way to yank text into the anonymous copy buffer (or "register" as it's called in vi).
The "Zen" of vi is that you're speaking a language. The initial y is a verb. The statement yy is a simple statement which is, essentially, an abbreviation for 0 y$:
0 go to the beginning of this line.
y yank from here (up to where?)

  
## .block
license: mit

## .block
license: mit

## .block
license: mit
	[user]
	name = Pavan Kumar Sunkara
	email = pavan.sss1991@gmail.com
	[core]
	editor = vim
	whitespace = fix,-indent-with-non-tab,trailing-space,cr-at-eol
	excludesfile = ~/.gitignore
	[sendemail]
	smtpencryption = tls
	smtpserver = smtp.gmail.com
	<html>
	<head>
	<meta charset="UTF-8">
	<title>Bootstrap 3 Essential</title>
	<meta http-equiv="X-UA-Compatible" content="IE=edge">
	<meta name="viewport" content="width=device-width, initial-scale=1">
	<link rel="stylesheet" href="css/bootstrap.min.css">
	<link rel="stylesheet" type="text/css" href="css/styles.css">