From d69f0f5e425930652e450eb1c383089ae6bdea4d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Pi=C3=B1a=20Colada?= Date: Thu, 20 May 2021 09:35:19 +0530 Subject: [PATCH] Updated Concepts (markdown) --- Concepts.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Concepts.md b/Concepts.md index 778be77..50bf588 100644 --- a/Concepts.md +++ b/Concepts.md @@ -48,11 +48,11 @@ or a Bash function (with ^\\ as dvtm modifier) to handle arguments: Sessions are a way to save and restore states of work. A session stores the settings and contexts. -Sessions can be loaded dynamically at runtime or with a [program option](https://github.com/jarun/nnn/wiki/Usage#program-options). +Sessions can be loaded at runtime or with a [program option](https://github.com/jarun/nnn/wiki/Usage#program-options). Notes: -1. When a session is loaded dynamically, the last working state is saved automatically to a dedicated -- "auto session" -- session file. The "auto session" is also used in persistent session mode if no session is loaded explicitly. +1. When a session is loaded at runtime, the last working state is saved automatically to a dedicated -- "auto session" -- session file. The "auto session" is also used in persistent session mode if no session is loaded explicitly. 2. Listing input stream has a higher priority to session options (`-s`/`-S`). Sessions can be loaded explicitly at runtime. Session option _restore_ would restore the "auto session" at runtime. 3. The persistent session option is global. If it is used, the last active session will be updated with the final state at program quit.