nnn

Unnamed repository; edit this file 'description' to name the repository.
Log | Files | Refs | README | LICENSE

commit 7086df5c784f2ad1f14408f2e9df9ff41b4a4af1
parent f9d38d1420298ac2a12fe7dce307397cea82e208
Author: Arun Prakash Jana <engineerarun@gmail.com>
Date:   Thu, 16 Jan 2020 20:19:21 +0530

Update docs

Diffstat:
MREADME.md | 1+
Mplugins/README.md | 2++
2 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/README.md b/README.md @@ -33,6 +33,7 @@ It runs smoothly on the Pi, [Termux](https://www.youtube.com/watch?v=AbaauM7gUJw - Minimizes screen refresh with fast line redraws - Tiny binary (typically less than 100KB) - Portable + - Language-agnostic plugins - Minimal library deps, easily compilable, tiny binary - No config file, minimal config with sensible defaults - Widely available on many packagers diff --git a/plugins/README.md b/plugins/README.md @@ -10,6 +10,8 @@ Plugins extend the capabilities of `nnn`. They are _executable_ scripts (or binaries) which `nnn` can communicate with and trigger. This mechanism fits perfectly with the fundamental design to keep the core file manager lean and fast, by delegating repetitive (but not necessarily file manager-specific) tasks to the plugins. +`nnn` is language-agnostic when it comes to plugins. You can write a plugin in any (scripting) language you are comfortable in! + ## Installing plugins The following command installs or updates (after backup) all plugins: