GNU nano - Bugs: bug #55376, self-compiled nano does not read...
You are not allowed to post comments on this tracker with your current authentication level.
bug #55376: self-compiled nano does not read /etc/nanorc
Submitter: | Robert Johnson <alohawolf> | ||
Submitted: | Fri 04 Jan 2019 03:04:09 AM UTC | ||
Severity: | 3 - Normal | Status: | Invalid |
Assigned to: | None | Open/Closed: | Closed |
Jump to the original submission
Tue 07 Jan 2020 01:51:18 PM UTC, comment #8: |
Benno Schulenberg <bens> |
Tue 07 Jan 2020 04:46:26 AM UTC, comment #7: Bless this forum for pointing me in the right direction. I have voted my encouragement on bug #57061. Thank you all for addressing this. |
Carter Pape <carterpape> |
Wed 16 Oct 2019 08:18:46 AM UTC, comment #6: The suggestion for letting ./configure print the baked-in nanorc paths at its end has been posted as bug #57061. |
Benno Schulenberg <bens> |
Sat 05 Jan 2019 04:51:39 PM UTC, comment #5: So, pidgin takes this strategy.
|
Robert Johnson <alohawolf> |
Sat 05 Jan 2019 04:10:31 PM UTC, comment #4: Printing the configured paths... Good idea. But do you have any example of a package that does this? Because when I add at the end of configure.ac:
|
Benno Schulenberg <bens> |
Fri 04 Jan 2019 07:38:03 PM UTC, comment #3: ahha!
|
Robert Johnson <alohawolf> |
Fri 04 Jan 2019 06:55:53 PM UTC, comment #2: The most likely cause is that you have built nano with a default run of ./configure, which means that nano will not read /etc/nanorc but will instead read /usr/local/etc/nanorc. If the latter does not exist, nano will still read the .nanorc in your homedir. The prudent thing to do is thus: put all your configuration in the .nanorc file in your homedir and forget about any global configuration. |
Benno Schulenberg <bens> |
Fri 04 Jan 2019 03:07:21 AM UTC, comment #1: incidentally, I find the same behavior on MacOS, when building 3.2 from homebrew. |
Robert Johnson <alohawolf> |
Fri 04 Jan 2019 03:04:09 AM UTC, original submission:
I have an Ubunu 16.04 system that I build nano-3.2 from sources on, I updated my nanorc to reflect the correct location of the syntax highlight files, and I was unable to get any colors at all.
|
Robert Johnson <alohawolf> |
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 9 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2019-10-16 | bens | Open/Closed | Open | Closed | |
2019-01-05 | alohawolf | Attached File | - | Added pidginconfiglog.txt, #45876 | |
Attached File | - | Added pidgin-configure.ac, #45877 | |||
Attached File | - | Added pidgin-configure, #45878 | |||
2019-01-05 | bens | Status | None | Invalid | |
Summary | Colors not working on 3.2 | self-compiled nano does not read /etc/nanorc | |||
2019-01-04 | alohawolf | Attached File | - | Added nanorc, #45861 | |
2019-01-04 | alohawolf | Attached File | - | Added nanoconfigureresults.txt, #45859 | |
Attached File | - | Added nanomakeresults.txt, #45860 |
Powered by Savane 3.13-d3ae.
Corresponding source code
As a mitigation, I've added a FAQ item about this:
https://git.savannah.gnu.org/cgit/nano.git/commit/?id=194620c5.