| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Just highlight everything bad in dark red so it's not too distracting.
|
|
|
|
|
|
| |
This reverts commit 6d80bf50aac77ff951d0519bcb0cc9914131d933.
This appears to be useless; I'm not sure why I thought it worked.
|
|
|
|
|
| |
This saves sourcing syncolor.vim again, since we're probably going to be
doing that at least two more times.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I don't use gVim often, so I didn't notice this was missing. I think Vim
has been accommodating this omission until now with my hardcoded
'background' setting of "dark", since changed to use some conditional
logic:
>From ab104099db86661d1dcb86d58f1e318ae06dbb05 Mon Sep 17 00:00:00 2001
>From: Tom Ryder <tom@sanctum.geek.nz>
>Date: Sun, 29 Oct 2017 23:27:59 +1300
>Subject: [PATCH] Switch on COLORFGBG to get background lightness
>
>Now that this environment variable is kept and updated in tmux after
>54553ae, we should be able to either configure terminals or explicitly
>set it during startup if we want to use lighter terminals.
>
>I'm much more comfortable with this than simply hardcoding it in the
>configuration.
>
>This doesn't solve the problem of carrying the environment variable over
>an SSH session, however, but I'm not really sure there's a solution to
>that besides configuring sshd(8) itself to accept these variables in
>transit.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
I've made this same mistake before, too ...
|
| |
|
| |
|
|
|
| |
Show the cursor line with a faint background and not an ugly and hard-to-see underline when `cursorline` is set.
|
|
|
|
| |
Signed-off-by: Tom Ryder <tom@sanctum.geek.nz>
|
| |
|
| |
|
|
chopped everything up. Oh well.
|