nano-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Nano-devel] RFC: should restricted mode disallow --locking?


From: Benno Schulenberg
Subject: [Nano-devel] RFC: should restricted mode disallow --locking?
Date: Fri, 23 Mar 2018 19:37:50 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0

Hi all,

In restricted mode (-R, --restricted), nano goes to great lengths
to prevent the user from opening or accessing any file that was
not given on the command line: nanorc files are not read, backup
files are not made, history files are not read nor written, the
file browser and spell checking and the linter are disabled...

*But*, the option -G (--locking) is still available, so nano will
read and/or write a lock file for each file given on the command
line.

Should this be disabled too?  Or is file locking somehow useful
when in restricted mode?

Benno

Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]