Re: How to compile with --enable-nanorc?
flomanstrategy <[email protected]> Thu, 5 Dec 2019 23:31:15 +0100
| Newsgroups | gmane.editors.nano.general |
|---|---|
| Message-ID | <CAFJGo16exNTMYja44OXOqibrCjbFayPtTQNXoT+3o1aZ6wf=Aw@mail.gmail.com> |
Alright, I think you nailed it with your lasthcomment I did what you said and now it's fixed !! I had to put the right prefix (/usr) though, didn't know And thank you for the strace command! Le jeu. 5 déc. 2019 à 20:10, flomanstrategy <[email protected]> a écrit : > I answered only to help-nano (hope it's fine) > > I chose 2.9.8 because it's the latest version that doesn't need new debian > 10 packages (i'm on debian 9) to avoid conflicts > > > which nano > /usr/local/bin/nano > > Another problem I have is when I type "dpkg -r nano" it says this > dpkg: warning: ignoring request to remove nano, only the config > files of which are on the system; use --purge to remove them too > > > > strace nano README 2>TRAIL; grep -n access TRAIL | grep -n nanorc | less > 7:62:access("/usr/local/etc/nanorc", R_OK) = -1 ENOENT (No such file or > directory) > 8:64:access("/home/my_server/.nanorc", R_OK) = -1 ENOENT (No such file or > directory) > 9:65:access("/home/my_server/.config/nano/nanorc", R_OK) = -1 ENOENT (No > such file or directory) > > Ok seems like it doesn't look in the right directory > > > Did you maybe compile and install nano at first without the --prefix=/usr > option? If yes, then you need to configure it again without that option > and run 'make uninstall', to get rid of the nano in /usr/local/bin/. > > And YES. I don't know where it should install normally, I found the prefix > here > https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/nano > so that may be it > I just tried to "make uninstall" (with and without sudo), it did > something but nano is still installed on 2.9.8 after that > > Le jeu. 5 déc. 2019 à 16:41, Benno Schulenberg <[email protected]> a > écrit : > >> >> Op 05-12-2019 om 13:53 schreef Benno Schulenberg: >> > Which nano is this running? You can find out with 'which nano', >> > or with 'type - nano'. >> >> I meant: 'type -a nano'. >> >> Benno >> >>