Immanuel/nnn: My build of nnn with minor changes - nnn

My build of nnn with minor changes

lostd 0548a181e6 Test for when permissions change while browsing		9年前
LICENSE	Update dates	10年前
Makefile	Make config independent to avoid accidental overwrites	9年前
README	Update contact information in README	10年前
config.def.h	Key bindings to run user-defined commands	10年前
mktest.sh	Test for when permissions change while browsing	9年前
noice.1	Key bindings to run user-defined commands	10年前
noice.c	Refactor parts of browse() into populate() and redraw()	9年前
strlcat.c	Replace asprintf() with strlcpy() and strlcat()	10年前
strlcpy.c	Add strlcpy()	10年前
util.h	Remove unused include	10年前

README

               __
  ___     ___ /\_\    ___     __
/' _ `\  / __`\/\ \  /'___\ /'__`\
/\ \/\ \/\ \L\ \ \ \/\ \__//\  __/
\ \_\ \_\ \____/\ \_\ \____\ \____\
 \/_/\/_/\/___/  \/_/\/____/\/____/
                                    -- by lostd and sin
=======================================================


What is it?
===========

noice is a small ncurses-based file browser.
It was first developed to be used with a tv remote control for a media
center solution.


Getting started
===============

Get the latest version from the git-repository; build and install it.  Run
noice in a directory to display its content in the form of a list, where
each line is a file or directory.  The currently selected item will be
preceded with a " > " by default.

For more information refer to the manpage.


Building
========

To build noice you need a curses implementation available.  In most
cases you just do:

    make

It is known to work on OpenBSD, NetBSD, FreeBSD, DragonFly BSD, Linux,
IRIX 6.5, Haiku, Solaris 9.  Some notes for building on certain systems
follow.

 * IRIX 6.5:
   Tested with gcc from http://freeware.sgi.com/.

    make CC="gcc" LDLIBS="-lgen -lcurses"

 * Haiku:

    make LDLIBS="-lncurses"

 * Solaris 9:
   Tested with gcc from http://www.opencsw.org/.

    export PATH=/usr/ccs/bin:/opt/csw/bin
    make CC="gcc"


Contact
=======

To report bugs and/or submit patches, you can reach us through
the freenode IRC network at #2f30 or by subscribing to tech@lists.2f30.org.