.nanorc Configuration Transition from Command-Line Flags

GNU nano allows users to configure the editor environment through both command-line arguments and persistent resource files. While flags like -l provide immediate activation of features such as line numbering, migrating these settings to a ~/.nanorc file is the standard approach for maintaining a consistent environment across sessions.

A potential conflict arises when a user defines a setting in the global /etc/nanorc file, overrides it in the local ~/.nanorc, and simultaneously passes a contradictory flag during startup. The interaction between these three layers of configuration—global, user-specific, and runtime arguments—determines the final editor state.

• Which configuration layer takes precedence when a specific toggle is defined in all three locations?
• Does a syntax error in the ~/.nanorc file cause the editor to fall back to global defaults or ignore all subsequent user-level overrides?