GNU nano - Bugs: bug #60307, [Request] nanorc.d style config
You are not allowed to post comments on this tracker with your current authentication level.
bug #60307: [Request] nanorc.d style config
Submitter: | Paul Chernysh-Barr <nassbar> | ||
Submitted: | Tue 30 Mar 2021 03:45:22 AM UTC | ||
Severity: | 1 - Wish | Status: | Wont Fix |
Assigned to: | None | Open/Closed: | Closed |
Tue 20 Apr 2021 09:29:27 AM UTC, comment #4: |
Benno Schulenberg <bens> |
Sun 04 Apr 2021 03:17:11 PM UTC, comment #3: I'm amazed. You work for an organisation that has its own developers, but you /request/ a feature instead of providing a patch? You want me to do your work for you, for free?
|
Benno Schulenberg <bens> |
Sat 03 Apr 2021 06:41:48 AM UTC, comment #2: In my organisation we have a number of admin, support, and developer staff that have differences of opinion on what should and shouldn't be configured.
|
Paul Chernysh-Barr <nassbar> |
Wed 31 Mar 2021 08:36:27 AM UTC, comment #1: You mean that any package (other than nano itself) could drop some nanorc fragment in /etc/nanorc.d/, and then nano would read it after /etc/nanorc has been read and before ~/.nanorc would be read? When would this be useful? Please give two examples. |
Benno Schulenberg <bens> |
Tue 30 Mar 2021 03:45:22 AM UTC, original submission:
This request is to add functionality to allow includes of system-wide configuration to override the configuration commonly in /etc/nanorc via something like including files in /etc/nanorc.d/* (purely for example).
|
Paul Chernysh-Barr <nassbar> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 3 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2021-04-28 | bens | Open/Closed | Open | Closed | |
2021-04-20 | bens | Status | None | Wont Fix | |
2021-03-31 | bens | Severity | 3 - Normal | 1 - Wish |
Powered by Savane 3.13-02a9.
Corresponding source code
Nano is a user tool -- its configuration should be under full control of the user. In my opinion, system admins should not be modifying /etc/nanorc after the system has been first set up, nor should the installation of any other packages affect the way that nano works. So checking an /etc/nanorc.d/ directory is not a good idea (and would only waste time).