aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--files/.psqlrc1
-rw-r--r--files/.taskrc76
-rw-r--r--files/.vim/templates/=template=docker-compose.yml13
-rw-r--r--files/.vimrc2
-rw-r--r--files/.vit/config.ini208
-rw-r--r--files/.zsh/rc/S50_aliases5
-rw-r--r--files/.zsh/rc/S51_ledger2
-rw-r--r--install.conf.yaml2
8 files changed, 307 insertions, 2 deletions
diff --git a/files/.psqlrc b/files/.psqlrc
index 119026d..92ce556 100644
--- a/files/.psqlrc
+++ b/files/.psqlrc
@@ -17,6 +17,7 @@
\x auto
-- Maintain a separate history for each database.
\set HISTFILE ~/.psql_history- :DBNAME
+\set HISTSIZE 20000
\set HISTCONTROL ignoreboth
\unset QUIET
diff --git a/files/.taskrc b/files/.taskrc
new file mode 100644
index 0000000..852124a
--- /dev/null
+++ b/files/.taskrc
@@ -0,0 +1,76 @@
+# [Created by task 2.5.1 7/11/2020 00:44:31]
+# Taskwarrior program configuration file.
+# For more documentation, see http://taskwarrior.org or try 'man task', 'man task-color',
+# 'man task-sync' or 'man taskrc'
+
+# Here is an example of entries that use the default, override and blank values
+# variable=foo -- By specifying a value, this overrides the default
+# variable= -- By specifying no value, this means no default
+# #variable=foo -- By commenting out the line, or deleting it, this uses the default
+
+# Use the command 'task show' to see all defaults and overrides
+
+# ALIASES
+
+alias.@=context
+alias.@@=context none
+
+# MISCELLANEOUS
+
+search.case.sensitive=no
+active.indicator=>
+list.all.projects=yes
+nag=""
+
+# PROJECTS
+
+default.project=Inbox
+
+# CONTEXTS
+
+context.personal=project.not:Work
+context.home=project:Home
+context.work=project:Work
+context.ocrv=project:Work.Ocrv
+
+# DATES
+
+weekstart=Monday
+
+# URGENCY
+
+urgency.tags.coefficient=0
+urgency.annotations.coefficient=0
+
+# Swap none and low priorities
+uda.priority.values=H,M,,L
+urgency.uda.priority.L.coefficient=0
+urgency.uda.priority..coefficient=1.8
+
+# Files
+data.location=~/.task
+
+# Color theme (uncomment one to use)
+#include /usr/share/taskwarrior/light-16.theme
+#include /usr/share/taskwarrior/light-256.theme
+#include /usr/share/taskwarrior/dark-16.theme
+#include /usr/share/taskwarrior/dark-256.theme
+#include /usr/share/taskwarrior/dark-red-256.theme
+#include /usr/share/taskwarrior/dark-green-256.theme
+#include /usr/share/taskwarrior/dark-blue-256.theme
+#include /usr/share/taskwarrior/dark-violets-256.theme
+#include /usr/share/taskwarrior/dark-yellow-green.theme
+#include /usr/share/taskwarrior/dark-gray-256.theme
+#include /usr/share/taskwarrior/dark-gray-blue-256.theme
+#include /usr/share/taskwarrior/solarized-dark-256.theme
+include /usr/share/taskwarrior/solarized-light-256.theme
+#include /usr/share/taskwarrior/no-color.theme
+
+# Tasksh
+
+uda.reviewed.type=date
+uda.reviewed.label=Reviewed
+report._reviewed.description=Tasksh review report. Adjust the filter to your needs.
+report._reviewed.columns=uuid
+report._reviewed.sort=reviewed+,modified+
+report._reviewed.filter=( reviewed.none: or reviewed.before:now-6days ) and ( +PENDING or +WAITING )
diff --git a/files/.vim/templates/=template=docker-compose.yml b/files/.vim/templates/=template=docker-compose.yml
new file mode 100644
index 0000000..7e8b80f
--- /dev/null
+++ b/files/.vim/templates/=template=docker-compose.yml
@@ -0,0 +1,13 @@
+version: "3"
+services:
+
+ name:
+ image: imagename
+ container_name: name
+ restart: unless-stopped
+ environment:
+ - TZ=UTC
+ labels:
+ - "label=true"
+ volumes:
+ - ./data:/data
diff --git a/files/.vimrc b/files/.vimrc
index a3c9770..28887e6 100644
--- a/files/.vimrc
+++ b/files/.vimrc
@@ -67,6 +67,7 @@ Plugin 'sheerun/vim-polyglot'
Plugin 'terryma/vim-expand-region'
" Maintains a history of previous yanks, changes and deletes
"Plugin 'vim-scripts/YankRing.vim'
+Plugin 'tpope/vim-dadbod'
" File types
@@ -167,6 +168,7 @@ set pastetoggle=<F3>
set cursorline
set ttyfast
set mouse=a
+set shortmess+=Ic
set autoindent
set smartindent
diff --git a/files/.vit/config.ini b/files/.vit/config.ini
new file mode 100644
index 0000000..a5ab216
--- /dev/null
+++ b/files/.vit/config.ini
@@ -0,0 +1,208 @@
+# This is the user configuration file for VIT.
+
+# All configuration options are listed here, commented out, and showing their
+# default value when not otherwise set.
+
+# The format is standard INI file format. Configuration sections are enclosed
+# by brackets. Configuration values should be placed in their relevant section,
+# using a 'name = value' format. Boolean values can be expressed by the
+# following:
+# True values: 1, yes, true (case insensitive)
+# False values: All other values.
+
+
+[taskwarrior]
+
+# Full path to the Taskwarrior configuration file. Tilde will be expanded to
+# the user's home directory.
+# NOTE: This setting is overridden by the TASKRC environment variable.
+#taskrc = ~/.taskrc
+
+
+[vit]
+
+# The keybinding map to use. This maps actions registered with VIT to be fired
+# when the user presses the specific keys configured in the keybindings file.
+# Possible keybindings are in the 'keybinding' directory, and the setting's
+# value should be the filename minus the .ini extension. The default keybinding
+# configuration is modeled heavily on the legacy VIT keybindings, and inspired
+# by vi/vim.
+#default_keybindings = vi
+
+# The theme to use. This allows control over the colors used in the
+# application itself. Possible themes are in the 'theme' directory, and the
+# setting's value should be the filename minus the .py extension.
+# Note that the theme does not control any coloring related to tasks -- this
+# is controlled via the color settings in the Taskwarrior configuration.
+#theme = default
+
+# Boolean. If true, VIT will ask for confirmation before marking a task as done,
+# deleting a task, or quitting VIT. Set to false to disable the prompts.
+#confirmation = True
+
+
+# Boolean. If true, VIT will show the output of the task command and wait for
+# enter. If false, VIT will not show output of the task command after
+# modifications to a task are made.
+#wait = True
+
+# Boolean. If true, VIT will enable mouse support for actions such as selecting
+# list items.
+#mouse = False
+
+[report]
+
+# The default Taskwarrior report to load when VIT first starts, if no report
+# or filters are passed at the command line.
+#default_report = next
+
+# The default Taskwarrior report to load when VIT first starts, if filters are
+# passed at the command line with no report.
+#default_filter_only_report = next
+
+# Boolean. If true, reports with the primary sort of project ascending will
+# indent subprojects. If you use deeply nested subprojects, you'll probably
+# like this setting.
+#indent_subprojects = True
+
+# Boolean. If true, display report rows with alternating background colors.
+#row_striping = True
+
+
+[marker]
+
+# Boolean. Enables markers. Markers are configurable labels that appear on the
+# left side of a report to indicate information about a task when the displayed
+# report does not contain the related column.
+# For example, let's suppose you have a 'notes' UDA configured. You'd like to
+# see some indication that a task has a note, without displaying the full note
+# column in reports. You could configure a marker for that custom UDA as
+# follows:
+# uda.notes.label = (N)
+# Then, when a listed task has a note associated with it, you'll see the
+# marker '(N)' displayed in the leftmost column of any report that displays the
+# task in question.
+#enabled = True
+
+# What columns to generate markers for. Can either be 'all' for all columns, or
+# a comma separated list of columns to enable markers for. Possible columns
+# are:
+# depends,description,due,project,recur,scheduled,start,status,tags,until
+#columns = all
+
+# The header label for the markers column when it is displayed.
+#header_label =
+
+# Boolean. If true, an associated color value must be configured in the
+# Taskwarrior configuration in order for the marker to be displayed. If false,
+# and no Taskwarrior color configuration is present for the matching marker,
+# then it is not displayed.
+# For example, if this is set to True, then for the above-mentioned 'notes'
+# marker to be displayed, a matching Taskwarrior color configuration for the
+# 'notes' UDA must be present, e.g.:
+# color.uda.notes=yellow
+#require_color = True
+
+# Boolean. If true, subprojects of a project will also display the configured
+# root project's marker, if the subproject itself does not have its own marker
+# configured.
+# For example, given the following projects:
+# Foo
+# Foo.Bar
+# If this value is set to True, and the Foo project has a configured marker,
+# then Foo.Bar would also display Foo's marker.
+#include_subprojects = True
+
+# Below are listed all of the available markers, with their default label.
+# To disable a specific marker, set its label to empty. Any section enclosed
+# in brackets should be replaced by the appropriate identifier, eg.
+# [project_name] with the actual name of a project.
+#active.label = (A)
+#blocked.label = (BD)
+#blocking.label = (BG)
+#completed.label = (C)
+#deleted.label = (X)
+#due.label = (D)
+#due.today.label = (DT)
+#keyword.label = (K)
+#keyword.[keyword_name].label =
+#overdue.label = (OD)
+#project.label = (P)
+#project.none.label =
+#project.[project_name].label =
+#recurring.label = (R)
+#scheduled.label = (S)
+#tag.label = (T)
+#tag.none.label =
+#tag.[tag_name].label =
+#uda.label =
+#uda.priority.label = (PR)
+#uda.[uda_name].label =
+
+
+[color]
+
+# Boolean. If true, use the colors in Taskwarrior's configuration to colorize
+# reports. Note that VIT uses a fundamentally different paradigm for
+# colorization, which combines tying coloring to associated report columns in
+# combination with markers (see above). This setting works independently of
+# Taskwarriors 'color' config setting.
+#enabled = True
+
+# Boolean. If true, subprojects of a project will also display the configured
+# root project's color, if the subproject itself does not have its own color
+# configured.
+# For example, given the following projects:
+# Foo
+# Foo.Bar
+# If this value is set to True, and the Foo project has a configured color,
+# then Foo.Bar would also display Foo's color.
+#include_subprojects = True
+
+# For the Taskwarrior color configuration, there are three special values:
+# color.project.none
+# color.tag.none
+# color.uda.[uda_name].none
+# If any of these are configured for color, then the label below will be used
+# in the related column to display the color configuration.
+#none_label = [NONE]
+
+
+[keybinding]
+
+# This section allows you to override the configured keybindings, associate
+# additional keybindings with VIT actions, and set up macros triggered by a
+# keybinding.
+
+# Meta keys are enclosed in angle brackets, variables are enclosed in curly
+# brackets. Keybindings here can either be:
+# - Associated with a single VIT action
+# - A macro that describes a series of key presses to replay
+
+# For VIT actions, the form is:
+# keys[,keys] = {ACTION_NAME}
+# For example, to associate the keybinding 'zz' with the undo action:
+# zz = {ACTION_TASK_UNDO}
+# To only disable a keybinding, use the special noop action:
+# w = {ACTION_NOOP}
+# wa = {ACTION_TASK_WAIT}
+# The above would disable the task wait action for the 'w' key, and instead
+# assign it to the 'wa' keybinding.
+
+# For a list of available actions, run 'vit --list-actions'.
+# A great reference for many of the available meta keys, and understanding the
+# default keybindings is the 'keybinding/vi.ini' file.
+
+# For macros, the form is:
+# keys[,keys] = keypresses
+# For example, to map the 'o' key to opening the OneNote script, passing it
+# the currently focused task UUID:
+# o = :!wr onenote {TASK_UUID}<Enter>
+
+# The special '{TASK_UUID}' variable can be used in any macro, and it will be
+# replaced with the currently highlighted task's UUID.
+
+# Multiple keybindings can be associated with the same action/macro, simply
+# separate the keybindings with a comma:
+# <Ctrl>z,zz = {ACTION_TASK_UNDO}
+q = Q
diff --git a/files/.zsh/rc/S50_aliases b/files/.zsh/rc/S50_aliases
index c06c572..fc94b21 100644
--- a/files/.zsh/rc/S50_aliases
+++ b/files/.zsh/rc/S50_aliases
@@ -29,6 +29,9 @@ alias zgrep='zgrep --color=auto'
alias fgrep='fgrep --color=auto'
alias egrep='egrep --color=auto'
alias fn='find . -name'
+alias ip='ip -color'
+alias dmesg='dmesg --human'
+alias ports='ss -tulanp'
alias ls='ls --color=auto -h -F --group-directories-first'
alias d='dirs -v | head -10'
@@ -80,7 +83,7 @@ alias gco="git branch | fzf | xargs git checkout"
alias rscp='rsync -avzP'
-alias yt-date='youtube-dl --output="[%(playlist_index)s] %(upload_date)s - %(title)s-%(id)s.%(ext)s"'
+alias yt-date='youtube-dl --download-archive=download-archive.log --ignore-errors --output="[%(playlist_index)s] %(upload_date)s - %(title)s-%(id)s.%(ext)s"'
alias yt-audio='youtube-dl --format bestaudio --embed-thumbnail --extract-audio --audio-format mp3'
alias boot-log="sed 's/\^\[/\o33/g;s/\[1G\[/\[27G\[/' /var/log/boot | less -r"
diff --git a/files/.zsh/rc/S51_ledger b/files/.zsh/rc/S51_ledger
index 12028ac..e66d744 100644
--- a/files/.zsh/rc/S51_ledger
+++ b/files/.zsh/rc/S51_ledger
@@ -16,7 +16,7 @@ _ledger_smartcase_expr() {
bal() {
if [ $# -eq 0 ] || [[ $1 =~ [-].+ ]] ; then
- ledger accounts | fzf --multi --preview "ledger balance $* {+}"
+ ledger balance --format '%(account)\n' ^Assets | sort | fzf --multi --preview "ledger balance $* {+}"
elif [ $# -eq 1 ] ; then
ledger balance \( ^Assets ^Liabilities \) and $(_ledger_smartcase_expr "$*")
else
diff --git a/install.conf.yaml b/install.conf.yaml
index 97fd3ea..cea00fb 100644
--- a/install.conf.yaml
+++ b/install.conf.yaml
@@ -13,6 +13,8 @@
~/.mpv: files/.mpv
~/.lessfilter.sh: files/.lessfilter.sh
~/.psqlrc: files/.psqlrc
+ ~/.taskrc: files/.taskrc
+ ~/.vit: files/.vit
# Git
~/.gitconfig: files/.gitconfig
~/.gitignore: files/.gitignore