af2a10fdc3
code pretty, too: * Use styles, color, and maybe a little positioning without necessarily clearing the whole screen first. * Leave more than one screenful of scrollback in the buffer after your program exits, like a well-behaved command-line app should. * Get rid of all those noisy, C-like calls to tigetstr and tparm, so your code doesn't get crowded out by terminal bookkeeping. * Act intelligently when somebody redirects your output to a file, omitting the terminal control codes the user doesn't want to see (optional).
11 lines
434 B
Text
11 lines
434 B
Text
@comment $NetBSD: PLIST,v 1.1 2017/04/12 11:41:44 adam Exp $
|
|
${PYSITELIB}/${EGG_INFODIR}/PKG-INFO
|
|
${PYSITELIB}/${EGG_INFODIR}/SOURCES.txt
|
|
${PYSITELIB}/${EGG_INFODIR}/dependency_links.txt
|
|
${PYSITELIB}/${EGG_INFODIR}/top_level.txt
|
|
${PYSITELIB}/blessings/__init__.py
|
|
${PYSITELIB}/blessings/__init__.pyc
|
|
${PYSITELIB}/blessings/__init__.pyo
|
|
${PYSITELIB}/blessings/tests.py
|
|
${PYSITELIB}/blessings/tests.pyc
|
|
${PYSITELIB}/blessings/tests.pyo
|