talwrii

jq cheatsheet

Extract field from list of objects

jq 'map(.foo)'

[ { foo: 1 }, { foo: 2 } ]
[1, 2]

talwrii

#!/bin/bash
# A stupid encrypted calculator

echo 'Creating private key'
openssl genrsa 1025 > /tmp/key.pem

echo 'Creating a request that a CA may sign'
openssl req -new -key /tmp/key.pem -config config > /tmp/cert-request 

echo 'Acting as a CA and self-signing certifate'

talwrii

;; yas-edit.el -- Quickly edit yas snippets
;; Copyright Tal Wrii (talwrii@gmail.com)
;; LICENSED UNDER GPLv3
(require 'yasnippet)

(defvar yas-edit-callback nil)
(defvar yas-edit-last nil "The last snippet expanded")

(defun yas-edit (prefix)
 (interactive "P")

talwrii

2017-04-13 Emacs meeting at skills matter

DISCLAIMER

These notes are the noter-takers interpretations of the interesting information in the talks.

The order of the material is not maintained, and some content is omitted.

Additional interpretation of the material has been added and though some of this is marked as such, other interpretations likely are not.

I would like to thank the authors for their talks.

talwrii

2017-04-13 Emacs meeting at skills matter

DISCLAIMER

These notes are the noter-taker’s interpretation of the interesting information in the talks.

The order of the material is not maintained, and some content is omitted. These notes were taken quite quickly so their may be factual errors

Additional interpretation of the material has been added and though some of this is marked as such, other interpretations likely are not.

I would like to thank the authors for their talks.

talwrii

;;; dump-keys.el -- Output emacs keybindings in a format suitable for grepping
;;; Maintained by Tal Wrii
;;; Copyright Tal Wrii 2017
;;; Copyright Justin Burkett 2015 (redistributed under GPLv3)

;;; This is highly influenced by Justin Burkett's which-keys.el
;;; and used its code as starting point
;;; Justin Burkett therefore  has copyright over some of this code (as does Tal Wrii)

;;; Tal Wrii is of course responsible for everything bad about this code

talwrii

Rules to write a better commit message

These are my preferences for a good commit message, feel free to fork this gist and add your own standards, or add comment here to share yours with the community.

1. Include only the files related to the feature you are implementing:

• Don't add any file that is not related to the main issue, you can make it in a separate commit.
• Separating files that not related is important in the revert cases.
• Revise the whole changes always before committing and make sure to mention each change you made in the message.

2. Commit subject should be concise and reflect the essence of the commit:

• Imagine the commit as an Email to the owner or your team mates.
• Subject in the first and main sentence of the commit, it should be concise and to the point.
• It shouldn't exceed 50 char.