aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Ryder <tom@sanctum.geek.nz>2019-05-18 13:27:50 +1200
committerTom Ryder <tom@sanctum.geek.nz>2019-05-18 13:27:50 +1200
commit99ef813ceb7d21c4a90b376db118fcc1dfa08ff6 (patch)
tree5bf0b211c389c5788605d5fbcc37708f451a6574
parentMerge branch 'release/v4.32.0' into develop (diff)
downloaddotfiles-99ef813ceb7d21c4a90b376db118fcc1dfa08ff6.tar.gz
dotfiles-99ef813ceb7d21c4a90b376db118fcc1dfa08ff6.zip
Quote things in ISSUES.md to appease spellchecker
-rw-r--r--ISSUES.md18
1 files changed, 9 insertions, 9 deletions
diff --git a/ISSUES.md b/ISSUES.md
index b2601de9..a4bb0ccb 100644
--- a/ISSUES.md
+++ b/ISSUES.md
@@ -1,16 +1,16 @@
Known issues
============
-* man(1) completion doesn't work on OpenBSD as manpath(1) isn't a thing on that
- system; need to find some way of finding which manual directories should be
- searched at runtime, if there is one.
-* The checks gscr(1df) makes to determine where it is are a bit naïve (don't
+* `man(1)` completion doesn't work on OpenBSD as `manpath(1)` isn't a thing on
+ that system; need to find some way of finding which manual directories should
+ be searched at runtime, if there is one.
+* The checks `gscr(1df)` makes to determine where it is are a bit naïve (don't
work with bare repos) and could probably be improved with some appropriate
- git-reflog(1) calls
-* dr(6df) is probably more practical in awk
+ `git-reflog(1)` calls
+* `dr(6df)` is probably more practical in awk
* Running the block of git(1) commands in the prompt leaves five "stale"
jobspecs around that flee after a jobs builtin run; only saw this manifest
- after 90dcadf; either I understand job specs really poorly or this may be a
+ after `90dcadf`; either I understand job specs really poorly or this may be a
bug in bash
* I can't find a clean way of detecting a restricted shell for ksh instances to
prevent trying to load anything fancy (works for Bash)
@@ -26,7 +26,7 @@ Known issues
depends on which shell you're using; the `sd` function isn't available when
you're not using Bash. Maybe I should try to extend `help` without breaking
it?
-* The b:undo\_indent definition for the perl filetype can probably be pushed
- upstream.
+* The `b:undo\_indent` definition for the `perl` filetype can probably be
+ pushed upstream.
* The `_text_filenames` completion handler for Bash won't work on files with
newlines in their names. Can it be made to?