| Commit message (Collapse) | Author | Age |
... | |
|
|
|
| |
type is an alias for whence -v and is more for human consumption.
|
|
|
|
| |
Keeps paths valid (from somehwere) rather than abrupt truncation.
|
|
|
|
| |
Why is there no easy way to *edit* an encrypted file?
|
|
|
|
|
| |
Unfortunately as far as I know I can't have it automatically sort them
after I hit escape.
|
|
|
|
| |
Begone, bloat shell.
|
|
|
|
|
| |
This fixes the prompt for FreeBSD's /home shenanigans. This is the one
thing that just seems dirty to me in FreeBSD. Why.
|
|
|
|
|
| |
ksh doesn't do sophisticated tab-complete so I have to actually type
ssh hosts now.
|
|
|
|
| |
Oops.
|
|
|
|
|
|
|
|
|
| |
Including the \r in the delimeters works properly in every version of
ksh I have. Awesome.
Also switch to emacs editing mode because it works better and I know how
to use it now. And set CDPATH with an empty item so it doesn't print the
expansion all the time.
|
|
|
|
|
| |
Kind of annoying to need two files, but for now I want to maintain
compatibility with all ksh implementations.
|
|
|
|
|
| |
You know, it's nice to be able to actually read the man page for your
shell.
|
| |
|
|
|
|
| |
zsh is not really my aesthetic, so I'm trying out ksh.
|
| |
|
| |
|
|
|
|
|
| |
Otherwise manUnderline counts as "cleared" so the default in man.vim
takes over again.
|
| |
|
|
|
|
| |
Someone removed the trailing whitespace, I guess.
|
|
|
|
|
| |
neovim 0.3.0 just doesn't give a shit anymore about how many colors your
terminal supports.
|
|
|
|
| |
I have no idea why I've kept on typing this out.
|
|
|
|
|
| |
Neovim is really dumb about how it interprets the names, and at this
point I actually know the order the colors are in.
|
| |
|
| |
|
|
|
|
| |
Time to see what it's like to be a hard-tab person.
|
| |
|
|
|
|
|
| |
Also replaced ~/.cargo/bin with a symlink to ~/.local/bin to avoid
having to have that in $path as well.
|
|
|
|
| |
Special characters in strings are more like normal code than keywords.
|
|
|
|
|
| |
Previously neovim would use these automatically if it found them, but
now it only checks for them on macOS. pbd continues to work well.
|
|
|
|
| |
I don't know why I've avoided having one for so long.
|
| |
|
| |
|
|
|
|
|
|
|
| |
This reverts commit 13ff37b0c37b6f0504ac45caf7fb2f35a5c68524.
I think I'm just gonna shove a hack into .zshenv on my FreeBSD machines
to set TERM=xterm.
|
| |
|
| |
|
|
|
|
| |
Gray is broken on FreeBSD with TERM=xterm-256color...
|
| |
|
|
|
|
|
| |
This is probably a good idea, though I haven't run into a merge conflict
yet.
|
| |
|
|
|
|
|
| |
GDB has no idea what's going on if you run it on a Cocoa app, and it
turns out LLDB is pretty nice. Why does it get a bad reputation?
|
| |
|
| |
|
|
|
|
| |
White is not obvious enough.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Weirdly with t_Co = 16 yellow and bright white weren't showing up on
TERM=linux.
|
|
|
|
| |
It seemes I can't take my finger off the shift key fast enough.
|
| |
|
| |
|
| |
|