diff options
authorTom Ryder <tom@sanctum.geek.nz>2018-11-22 22:42:16 +1300
committerTom Ryder <tom@sanctum.geek.nz>2018-11-22 22:42:16 +1300
commit234bcd5ee82cfb2f8fe42d1ae64eb9fa3cdfc5c2 (patch)
parentMerge branch 'release/v1.75.0' (diff)
parentBump VERSION (diff)
Merge branch 'hotfix/v1.75.1'v1.75.1
* hotfix/v1.75.1: Rebuild dotfiles(7df) manual
2 files changed, 34 insertions, 16 deletions
diff --git a/VERSION b/VERSION
index 8bfe5a2e..1c428430 100644
@@ -1,2 +1,2 @@
-tejr dotfiles v1.75.0
-Thu Nov 22 09:40:22 UTC 2018
+tejr dotfiles v1.75.1
+Thu Nov 22 09:42:06 UTC 2018
diff --git a/man/man7/dotfiles.7df b/man/man7/dotfiles.7df
index f6300f3a..ce341a07 100644
--- a/man/man7/dotfiles.7df
+++ b/man/man7/dotfiles.7df
@@ -76,6 +76,24 @@ The remaining files can be installed with the other \f[C]install\-*\f[]
Try \f[C]awk\ \-f\ bin/mftl.awk\ Makefile\f[] in the project's root
directory to see a list.
+.SS Configuration
+To save a set of \f[C]make\f[] targets useful for a specific user or
+host, you can save them in a newline\-separated file
+\f[C]~/.dotfiles.conf\f[], and install using that with the special
+\f[C]install\-conf\f[] target.
+This can include variable settings, too:
+$\ cd
+$\ cat\ .dotfiles.conf
+$\ make\ \-C\ .dotfiles\ install\-conf
.SS Tools
Configuration is included for:
@@ -244,8 +262,7 @@ You can set \f[C]PROMPT_COLOR\f[], \f[C]PROMPT_PREFIX\f[], and
\f[C]PROMPT_SUFFIX\f[] too, which all do about what you'd expect.
If you start up Bash, Korn shell, or Z shell, and it detects that it's
-normally your \f[C]$SHELL\f[] is one of the other two, the prompt will
-display an appropriate prefix.
+not your login shell, the prompt will display an appropriate prefix.
This is all managed within the \f[C]prompt\f[] function.
There's some mildly hacky logic on \f[C]tput\f[] codes included such
@@ -302,6 +319,14 @@ second argument in \f[C]$PWD\f[], emulating a feature of the Zsh
.IP \[bu] 2
+Two editor wrapper functions:
+.RS 2
+.IP \[bu] 2
+\f[C]e()\f[] invokes \f[C]$EDITOR\f[], or \f[C]ed(1)\f[] if not set.
+.IP \[bu] 2
+\f[C]v()\f[] invokes \f[C]$VISUAL\f[], or \f[C]vi(1)\f[] if not set.
+.IP \[bu] 2
\f[C]bc()\f[] silences startup messages from GNU \f[C]bc(1)\f[].
.IP \[bu] 2
\f[C]ed()\f[] tries to get verbose error messages, a prompt, and a
@@ -450,14 +475,6 @@ The included \f[C]\&.Xresources\f[] file assumes that \f[C]urxvt\f[] can
use 256 colors and Perl extensions.
If you're missing functionality, try changing \f[C]perl\-ext\-common\f[]
to \f[C]default\f[].
-My choice of font is Ubuntu Mono (http://font.ubuntu.com/), but the file
-should allow falling back to the more common Deja Vu Sans
-Mono (https://dejavu-fonts.github.io/).
-I've found Terminus (http://terminus-font.sourceforge.net/) works well
-too, but bitmap fonts are not really my cup of tea.
-The Lohit Kannada font bit is purely to make ಠ_ಠ work correctly.
-( ͡° ͜ʖ ͡°) seems to work out of the box.
.SS tmux
These are just generally vi\-friendly settings, not much out of the
@@ -522,10 +539,11 @@ and installed via submodules instead.
I define a few of my own \f[C]:compiler\f[] scripts for
\f[C]~/.vim/compiler\f[], for use for checking and linting of
appropriate filetypes.
-Because checking (does it work?) and linting (is it well\-written?) are
-separate processes for me, I bind them separately with local leader
-maps; for example, \f[C]_c\f[] runs a \f[C]perl\ \-c\f[] syntax check of
-Perl scripts, and \f[C]_l\f[] runs a Perl::Critic check.
+Because checking (does it compile?) and linting (is it correct and
+well\-written?) are separate processes for me, I bind them separately
+with local leader maps; for example, for \f[C]perl\f[] filetypes,
+\f[C],c\f[] switches \f[C]makprg\f[] to \f[C]perl\ \-c\f[], and
+\f[C],l\f[] to \f[C]perlcritic\f[].
.SS Neovim
I test my configuration every now and then with the Neovim