aboutsummaryrefslogtreecommitdiff
path: root/IDEAS.markdown
diff options
context:
space:
mode:
authorTom Ryder <tom@sanctum.geek.nz>2017-02-04 14:30:48 +1300
committerTom Ryder <tom@sanctum.geek.nz>2017-02-04 14:30:48 +1300
commit1ccea6184566a6fe3f8a247f2bcd060e64b89694 (patch)
tree07506379c43c21e16275317b45b7149a10663ca7 /IDEAS.markdown
parentAdd an idea (diff)
downloaddotfiles-1ccea6184566a6fe3f8a247f2bcd060e64b89694.tar.gz
dotfiles-1ccea6184566a6fe3f8a247f2bcd060e64b89694.zip
Remove idea about --color switches
Nope, we really do need to test the terminal. The source for GNU grep(1) even says (grep.c): >It would be impractical for GNU grep to become a full-fledged terminal >program linked against ncurses or the like, so it will not detect >terminfo(5) capabilities.
Diffstat (limited to 'IDEAS.markdown')
-rw-r--r--IDEAS.markdown4
1 files changed, 0 insertions, 4 deletions
diff --git a/IDEAS.markdown b/IDEAS.markdown
index f9071fc4..664181ee 100644
--- a/IDEAS.markdown
+++ b/IDEAS.markdown
@@ -14,7 +14,3 @@ Ideas
* ad() could be more intelligent; if there's only one directory that matches
the *whole pattern*, we can assume it's safe to use that one, rather than
stopping each time any node has more than one match
-* It seems likely that testing the terminal with tput to check if we can use
- --color with GNU grep(1) or ls(1) is overkill--I suspect it probably tests
- that internally, which would simplify the function wrappers. Need to check
- the source probably.