| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| | |
* feature/bin-review:
Refactor clog(1df), allow args and non-term stdin
Reimplement bl(1df) in Awk
|
| |
| |
| |
| |
| | |
This makes a bit clearer how awkward the rlwrap(1) code is, too. It may
not be worth keeping it.
|
|/
|
|
| |
This is shorter and tidier.
|
|\
| |
| |
| |
| |
| |
| | |
* feature/ax-safety:
Separate ax(1df) manpage args from command
Make newline explicit for ax(1df)
Make first ax(1df) arg safer, warn on second arg
|
| |
| |
| |
| |
| |
| |
| |
| | |
Just for a clearer visual distinction. This probably needs to be done
for other manual pages, too.
We use zero-width characters (\&) at the start of the lines beginning
with apostrophes so that they get printed literally.
|
| |
| |
| |
| |
| | |
This makes it a little more flexible, if you genuinely don't want a
newline in the output.
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
The format in the first argument does not need to be evaluated, so it
can be passed in a simple awk variable.
The second argument is evaluated, by design, so code injection is
trivial. It's probably a good idea to warn users about this explicitly.
$ ax '0);system("cat /etc/passwd")'
Make the whole thing a little terser, too, with the awk program
construction, variable assignment, and invocation all on one line.
|
|\
| |
| |
| |
| | |
* feature/vim-doc-fix:
Correct monospaced blocks in Vim plugin docs
|
|/
|
|
| |
Close unclosed blocks, and remove an unwanted block.
|
|\
| |
| |
| |
| |
| |
| |
| | |
* hotfix/v0.22.1:
Bump version number to 0.22.1 (hotfix)
Allow specifying GnuPG --keyid-format at build
Rebuild dotfiles(7) manual page
Bump version number to 0.22.0
|
| | |
|
| |
| |
| |
| |
| | |
Old versions of gpg(1) don't support "none" as a --keyid-format; allow
specifying it as a Makefile variable KEYID_FORMAT.
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* release/v0.22.0:
Rebuild dotfiles(7) manual page
Bump version number to 0.22.0
Update key fingerprint for finger(1)
Use only fingerprints for GnuPG keys
Remove --batch option and wrapper for gpg(1)
|
| | | |
|
| |/
|/| |
|
|\ \
| | |
| | |
| | |
| | |
| | | |
* feature/gpg-fp-only:
Update key fingerprint for finger(1)
Use only fingerprints for GnuPG keys
|
| | | |
|
|/ /
| |
| |
| | |
The manual page for gpg(1) says this is the safest way to do it.
|
|\ \
| | |
| | |
| | |
| | | |
* feature/gpg-no-batch:
Remove --batch option and wrapper for gpg(1)
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
This was originally added to cut the decryption boilerplate, which no
longer seems to be an issue; I think that --quiet may be correctly
blocking it now. Even without this, it caused more problems than it
solved when gpg(1) genuinely did need user interaction from me, for
example for --update-trustdb.
|
|\ \
| | |
| | |
| | |
| | |
| | | |
* release/v0.21.0:
Rebuild dotfiles(7) man page from README
Bump version number to 0.21.0
|
| | |\
| | |/
| |/|
| | |
| | |
| | |
| | | |
* release/v0.21.0:
Rebuild dotfiles(7) man page from README
Bump version number to 0.21.0
Switch from newsbeuter to newsboat
|
| | | |
|
|/ / |
|
|\ \
| | |
| | |
| | |
| | | |
* feature/newsboat:
Switch from newsbeuter to newsboat
|
|/ /
| |
| |
| |
| |
| | |
Newsbeuter is no longer maintained:
<https://github.com/akrennmair/newsbeuter/commit/7c981f460d6c8c3690f140cbb279c277dc8f55fe>
|
|\ \
| | |
| | |
| | |
| | | |
* release/v0.20.0:
Bump verison number to 0.20.0
|
| | |\
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* release/v0.20.0:
Bump verison number to 0.20.0
Add some comments to vintrc
Make vim-vint allow saying ":set nocompatible"
Add install target for vim-vint
Update submodule paths
Add syntax checking with zsh -n for Z shell
Use consistent indentation for bulleted list items
Update sahara submodule
Correct a homophone error in a comment
|
|/ / |
|
|\ \
| | |
| | |
| | |
| | | |
* feature/vim-zsh-check:
Add syntax checking with zsh -n for Z shell
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
* feature/typofix:
Correct a homophone error in a comment
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
* feature/vim-vint-install:
Add some comments to vintrc
Make vim-vint allow saying ":set nocompatible"
Add install target for vim-vint
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Per 62d2a7d, I need to have 'nocompatible' set if Vim is invoked as "ex"
or if it's sourced directly with the -u option. I disagree with the
policy.
|
|/ / / / |
|
|\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | | |
* feature/vim-submodule:
Update submodule paths
|
|/ / /
| | |
| | |
| | |
| | | |
Renamed two of my Vim submodules with the usual "vim-" prefix; this
avoids the 301 HTTP redirect.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | | |
* hotfix/v0.19.1:
Bump VERSION
Restore 'nocompatible' set to vimrc
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
* feature/readme-indent:
Use consistent indentation for bulleted list items
|
|/ / / / |
|
|\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | | |
* feature/vim-plugin-update:
Update sahara submodule
|
|/ / / |
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
* release/v0.19.0:
Bump version number to 0.19.0
|
| | | |\
| | | |/
| | |/|
| | | |
| | | |
| | | | |
* hotfix/v0.19.1:
Bump VERSION
Restore 'nocompatible' set to vimrc
|
| | | | |
|
| | |/
| | |
| | |
| | |
| | |
| | | |
Otherwise, the line-continuation in the ~/.vimrc fails if compatibility
mode survives the invocation step, for example if the vimrc file is
sourced directly with the -u option, or if vim is invoked as "ex".
|
| | |\
| | |/
| |/|
| | |
| | |
| | |
| | | |
* release/v0.19.0:
Bump version number to 0.19.0
Add `php -l` check binding for PHP filetype
Correct "fi" to "endif" in new compiler files
|
|/ / |
|