yegappan

Vim Script for Python Developers

This is a guide to Vim Script development for Python developers. Sample code for the various expressions, statements, functions and programming constructs is shown in both Python and Vim Script. This is not intended to be a tutorial for developing Vim scripts. It is assumed that the reader is familiar with Python programming.

For an introduction to Vim Script development, refer to usr_41.txt, eval.txt and Learn Vimscript the Hard Way

For a guide similar to this one for JavaScript developers, refer to Vim Script for the JavaScripter

This guide only describes the programming constructs that are present in both Python and Vim. The constructs that are unique to Vim (e.g. autocommands, [key-mapping](https://vimhelp.org/map.txt.html#key-m

HKGx

// ==UserScript==
// @name         █▬█ █ ▀█▀
// @namespace    https://github.com/HKGx
// @version      1.1
// @description  Make every discount a █▬█ █ ▀█▀
// @author       HKG
// @match        https://store.steampowered.com/*
// @grant        none
// @downloadURL  https://gist.github.com/HKGx/7958a6d18d1128ae4dd5f5e365ab5094/raw/65d7756558257ff440a4843a90f825ef0970e789/█▬█ █ ▀█▀.user.js
// @updateURL    https://gist.github.com/HKGx/7958a6d18d1128ae4dd5f5e365ab5094/raw/65d7756558257ff440a4843a90f825ef0970e789/█▬█ █ ▀█▀.user.js

XiangGaoMSFT

name: View Names
description: Sample script to list all names
author: xianggaomsft
host: EXCEL
api_set: {}
script:
    content: |
        $("#refresh").click(() => tryCatch(refresh));

        async function refresh() {

erlepereira

Assuming a Properly configured DNSMasq

a quickstart for dnsmasq is given at the end if you have not set it up yet.

---

something like this will add a great regularly updated malware file for it to use. More security and privacy to you! Specifically, this uses https://github.com/StevenBlack/hosts Choose one of the Raw Hosts file from there to use.

To setup DNSMasq, follow the below ...

wget -O- https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts | awk '$1 == "0.0.0.0" { print "address=/"$2"/0.0.0.0/"}' > /etc/dnsmasq.d/malware.conf`

romainl

Redirect the output of a Vim or external command into a scratch buffer

Usage (any shell)

Show full output of command :hi in scratch window:

:Redir hi

Show full output of command :!ls -al in scratch window:

mamcx

General

http://blog.pluralsight.com/elixir-is-for-programmers #Idea assert, test http://www.q-lang.io/ #Definicion tipos como campos DB http://dlang.org/exception-safe.html #Alternativa try--except con scope http://floodyberry.com/noncryptohashzoo/ #Implementaciones de funcion HASH https://github.com/mikeash/MAObjCRuntime/blob/master/main.m #Mejor runtime obj-c, extendible https://github.com/jspahrsummers/libextobjc #Similar https://github.com/Midar/objfw/ #Implementacion de obj-c portable http://swtch.com/~rsc/regexp/regexp1.html #Mejor que regex http://swannodette.github.io/2013/07/12/communicating-sequential-processes/ #Fundamentos CSP

abravalheri

Commit Message Guidelines

In the last few years, the number of programmers concerned about writing structured commit messages have dramatically grown. As exposed by Tim Pope in article readable commit messages are easy to follow when looking through the project history. Moreover the AngularJS contributing guides introduced conventions that can be used by automation tools to automatically generate useful documentation, or by developers during debugging process.

This document borrows some concepts, conventions and even text mainly from these two sources, extending them in order to provide a sensible guideline for writing commit messages.

• Goals
• Proposal
  • Commit Message Format

• Allowed ``

Avaq

const I  = x => x
const K  = x => y => x
const A  = f => x => f (x)
const T  = x => f => f (x)
const W  = f => x => f (x) (x)
const C  = f => y => x => f (x) (y)
const B  = f => g => x => f (g (x))
const S  = f => g => x => f (x) (g (x))
const S_ = f => g => x => f (g (x)) (x)
const S2 = f => g => h => x => f (g (x)) (h (x))

spion

Node streams - a fractal of weird design

and a potential refactor that could fix that

This is a list of issues and confusions I've encountered with node streams, and things I wish were designed and implemented differently. If promise-streams is ever going to change to a design that doesn't build on top of node streams, this would be a list of mistakes to avoid

1. enc parameter - Why is encoding always passed together with the data? It should be a separate concern. It doesn't even make sense in objectMode
2. eventemitter base - This encourages a lot of random events to be "attached" by other authors which doesn't work. Best to have an uniform (typed) interface so that everyone knows what to expect.
3. relying on nextTick etc for execution order - This is very unreliable and causes all sorts of unpredictable rules for implementers which are not documented anywhere. When you attach listeners determines what will happen.
4. no error propagation - we need the

kchida

- What do Etcd, Consul, and Zookeeper do?
  - Service Registration:
    - Host, port number, and sometimes authentication credentials, protocols, versions
      numbers, and/or environment details.
  - Service Discovery:
    - Ability for client application to query the central registry to learn of service location.
  - Consistent and durable general-purpose K/V store across distributed system.
    - Some solutions support this better than others.
    - Based on Paxos or some derivative (i.e. Raft) algorithm to quickly converge to a consistent state.
    - Centralized locking can be based on this K/V store.