augustohp

VIM para usuários Git

A intenção desse post é melhorar, se possível, seu workflow com o [Git][] se ele atualmente ele consiste de:

1. Usar o [Git][] através de uma shell de sua escolha.
2. Usar o [VIM][] como [editor padrão][2] [no Git][1].

Se você usa alguma ferramenta gráfica (tig também conta), eu não quero saber. Se você usa o [Git][] numa shell em conjunto com outro editor, procuro ansiosamente seu comentário me convencendo a trocar. :)

Preparando o VIm

alganet

# Main file, loads dependencies and holds application code

# Usage:
# $ git clone https://gist.github.com/a22a1373dcee7c175d1e.git
# $ cd a22a1373dcee7c175d1e
# $ chmod +x 00-index.sh
# $ ./00-index.sh
#
# Use sudo if your machine denies an address to netcat
#

nelsonsar

function GoToTest(...)
  let filename = expand('%:t:r')
  let test_filename = filename."Test.php"
  "You can use a folder to avoid tabf to open the wrong file
  if a:0 > 0
    execute "tabf **/".a:1."/".test_filename
  else
    execute "tabf **/".test_filename
  endif
endfunction

nelsonsar

<?php

class PosixErrorCode
{
    const EPERM           = 1;              /* Operation not permitted */
    const ENOENT          = 2;             /* No such file or directory */
    const ESRCH           = 3;             /* No such process */
    const EINTR           = 4;             /* Interrupted system call */
    const EIO             = 5;             /* Input/output error */
    const ENXIO           = 6;             /* Device not configured */

mapgen.js.coffee

# author: tmwhere.com

# --- third party dependencies
PIXI = require('pixi.dev')
_ = require('lodash')

noise = require('perlin').noise
Quadtree = require('quadtree').Quadtree
seedrandom = require('seedrandom')
# ---

augustohp

#!/usr/bin/env bash
#
# vim: et ts=4 sw=4 ft=sh:

declare -r SCRIPT_NAME=$0
declare -r THEME_LIGHT="Seashell"
declare -r THEME_DARK="Zenburn"
declare -r TAB_SPACES=4
declare -r LINE_NUMBER_COLUMN_LENGTH=4
declare -r OUTPUT_ENCODING=UTF-8

augustohp

/*! normalize.css v2.1.3 | MIT License | git.io/normalize */

/* ==========================================================================
   HTML5 display definitions
   ========================================================================== */

/**
 * Correct `block` display not defined in IE 8/9.
 */

denji

1. Download docker-compose.yml to dir named sentry
2. Change SENTRY_SECRET_KEY to random 32 char string
3. Run docker-compose up -d
4. Run docker-compose exec sentry sentry upgrade to setup database and create admin user
5. (Optional) Run docker-compose exec sentry pip install sentry-slack if you want slack plugin, it can be done later
6. Run docker-compose restart sentry
7. Sentry is now running on public port 9000

• https://docs.docker.com/compose/compose-file/#env_file

robertpainsi

Commit Message Guidelines

Short (72 chars or less) summary

More detailed explanatory text. Wrap it to 72 characters. The blank
line separating the summary from the body is critical (unless you omit
the body entirely).

Write your commit message in the imperative: "Fix bug" and not "Fixed
bug" or "Fixes bug." This convention matches up with commit messages

merikan

Some Jenkinsfile examples