dzintars

apiVersion: v1
kind: Pod
metadata:
  name: jenkins
  labels:
    app: jenkins
spec:
  restartPolicy: Always
  containers:
    - name: jenkins-server

dzintars

FZF

Move up/down in results - ctrl+j and ctrl+k

Open file in vertical split - ctrl+v

Open file in horizontal split - ctrl+x

Open file in new tab - ctrl+t

dzintars

#!/bin/sh

# Author: Dzintars Klavins
# This script will setup GitHub with multiple SSH identities
# Don't forget to make this file executable

# Setup multiple SSH identities for different Git accounts (with different credentials)
# Empty content of file
> ~/.config/Code/User/settings.json
# Place configuration in file.

dzintars

Collection of things you can do with AsciiDoc in GitHub

dzintars

Set WshShell = CreateObject("WScript.Shell")
MsgBox ConvertToKey(WshShell.RegRead("HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\DigitalProductId"))

Function ConvertToKey(Key)
Const KeyOffset = 52
i = 28
Chars = "BCDFGHJKMPQRTVWXY2346789"
Do
Cur = 0
x = 14

dzintars

Bazel Typescript

To avoid ../../../../../../filename.ts garbage in the source code you can use Typescript Path Aliases. This approach not only cleans up your imports but also helps when making refacoring and moving packages/modules around. No matter where you will place your package, all imports allways will be resolvable.

But this is not enought at runtime. For example if you want to run WebPack dev-server. By default webpack does not know how to resolve those imports. You need to tweak WebPack config

Other resources:

dzintars

#!/bin/bash

# Author: Dzintars Klavins
# This script will delete all network connections and devices.
# WARNING!!! Network connection will be lost!

# Delete all existing connections.
# All credits to: https://www.rene-pickhardt.de/index.html%3Fp=1955.html
for i in `nmcli c | \
grep -o -- "[0-9a-fA-F]\{8\}-[0-9a-fA-F]\{4\}-[0-9a-fA-F]\{4\}-[0-9a-fA-F]\{4\}-[0-9a-fA-F]\{12\}"` ; \

dzintars

#!/bin/sh

# Author: Dzintars Klavins
# This script will install Protoc compiler
# Don't forget to make this file executable

###################################
# Protocol Buffers  installation  #
###################################

dzintars

In a `~/.config/qutebrowser/config.py

config.set("fileselect.handler", "external")
config.set("fileselect.single_file.command", ['alacritty', '--class', 'ranger', '-e', 'ranger', '--choosefile', '{}'])
config.set("fileselect.multiple_files.command", ['alacritty', '--class', 'ranger', '-e', 'ranger', '--choosefile', '{}'])

In a ~/.config/sway/config

for_window [app_id="ranger"] floating enable

dzintars

My Neovim setup

https://github.com/oswee/prime/ansible/custom/roles/nvim

Structure

99% of the config examples i saw in the wild gives me a feeling that people actually don't know what they are doing with Neovim configuration. Neither I do. But I am questioning myself: How to structure configuration in a clean, modular, swappable, easy to read and navigate way. There, in the wild, I see things like: "Throw it all in a single file", "Plugins are evil, vanilla Vim is all I need", "I will leave that dead code for the reference in case if I need it",