bugGNU nano - Bugs: bug #57061, [Request] at the end of...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #57061: [Request] at the end of ./configure, print the baked-in nanorc paths

Submitter:  Benno Schulenberg <bens>
Submitted:  Wed 16 Oct 2019 08:17:19 AM UTC
Votes: 10
 
Severity:  1 - Wish Status:  Fixed
Assigned to:  bens Open/Closed:  Closed

Thu 30 Jul 2020 07:12:25 AM UTC, comment #4: 

Released in nano-5.0.

Benno Schulenberg <bens>
Group administrator
Sat 20 Jun 2020 12:11:37 PM UTC, comment #3: 

Fixed in git, commit bbdbf458, by adding a printing fragment at the end of Makefile.am (so that ./configure will make the proper substitions in it), and then at the very end of ./configure running that fragment.

Benno Schulenberg <bens>
Group administrator
Sun 19 Apr 2020 05:16:48 PM UTC, comment #2: 

Attached is a patch that prints out the path to the global nanorc file at the end of ./configure.  (Based on how ncurses does something similar.)

(file #48871)

Benno Schulenberg <bens>
Group administrator
Tue 04 Feb 2020 03:04:47 PM UTC, comment #1: 

Adding the following at the end of configure.ac before AC_OUTPUT:


eval CONFIGDIR=${sysconfdir}

AC_MSG_RESULT([])
AC_MSG_RESULT([    The system's nanorc file is: $CONFIGDIR/nanorc.])
if eval "test x$CURSES_LIB_NAME != x"; then
    AC_MSG_RESULT([    Using '$CURSES_LIB_NAME' as curses library.])
fi
AC_MSG_RESULT([])


and then running 'make', results in:


    The system's nanorc file is: NONE/etc/nanorc.
    Using 'ncursesw' as curses library.


And when then running ./configure with --prefix=/usr, it results in:


    The system's nanorc file is: /usr/etc/nanorc.
    Using 'ncursesw' as curses library.


This is wrong.  The autoconf documentation says that $sysconfdir and other such variables are meant to be used in the Makefiles, not during configure.  I don't see how this can be solved.

Benno Schulenberg <bens>
Group administrator
Wed 16 Oct 2019 08:17:19 AM UTC, original submission:  

(Original suggestion was made by Robert Johnson in bug #55376, comment #3.)

When nano is configured without the --prefix option, it is by default configure for a "local" install: at startup it will read /usr/local/etc/nanorc instead of /etc/nanorc.  For many users (including myself) this is unexpected and frustrating, because the self-compiled nano seems to ignore /etc/nanorc.

So, it would be nice if nano would print at the end of ./configure what paths the compiled nano will use for reading the two nanorc files.

Benno Schulenberg <bens>
Group administrator

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by bens
  • -email is unavailable- added by carterpape (I would like to see this item fulfilled. Not being able to find config file locations is frustrating.)
  • -email is unavailable- added by bens (Submitted the item)
  •  

    There are 10 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 7 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2020-07-30 bens Open/ClosedOpen Closed
    2020-06-20 bens StatusIn Progress Fixed
    2020-04-19 bens Attached File- Added 0001-build-make-.-configure-report-which-global-nanorc-fi.patch, #48871
        StatusNone In Progress
        Assigned toNone bens
        Carbon-Copy- Added alohawolf
    2020-01-07 carterpape Carbon-Copy- Added carterpape

    Back to the top

    Powered by Savane 3.13-4448.
    Corresponding source code