From b56db25a35cc677e6c2bce3f9293539dd5350abb Mon Sep 17 00:00:00 2001 From: Benno Schulenberg Date: Thu, 12 Dec 2019 19:17:22 +0100 Subject: [PATCH] docs: mention that all keywords in a nanorc file should be in lowercase --- doc/nano.texi | 1 + doc/nanorc.5 | 1 + 2 files changed, 2 insertions(+) diff --git a/doc/nano.texi b/doc/nano.texi index 93d25bb1..d641e951 100644 --- a/doc/nano.texi +++ b/doc/nano.texi @@ -695,6 +695,7 @@ be used to configure @command{nano} on startup without using command-line options. Additionally, there are some commands to define syntax highlighting and to rebind keys --- @pxref{Syntax Highlighting} and @ref{Rebinding Keys}. @command{nano} will read one command per line. +All commands and keywords should be written in lowercase. Options in nanorc files take precedence over @command{nano}'s defaults, and command-line options override nanorc settings. Also, options that do not diff --git a/doc/nanorc.5 b/doc/nanorc.5 index 062ada4d..b7509ed1 100644 --- a/doc/nanorc.5 +++ b/doc/nanorc.5 @@ -44,6 +44,7 @@ commands, which can be used to configure nano on startup without using command-line options. Additionally, there are some commands to define syntax highlighting and to rebind keys -- see the two separate sections on those. \fBnano\fP reads one command per line. +All commands and keywords should be written in lowercase. .sp Options in \fInanorc\fP files take precedence over nano's defaults, and command-line options override \fInanorc\fP settings. Also, options that