[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nano-devel] --disable-nanorc does not disable support and use of na
From: |
Mike Frysinger |
Subject: |
Re: [Nano-devel] --disable-nanorc does not disable support and use of nanorc |
Date: |
Thu, 27 Mar 2014 10:21:49 -0400 |
User-agent: |
KMail/4.12.3 (Linux/3.13.0; KDE/4.12.3; x86_64; ; ) |
On Thu 27 Mar 2014 11:30:24 Benno Schulenberg wrote:
> On Thu, Mar 27, 2014, at 1:58, Mike Frysinger wrote:
> > i think we need to barf when we get conflicting options. so in this case,
> > you want something like:
> >
> > --- a/configure.ac
> > +++ b/configure.ac
> > @@ -146,10 +146,17 @@ fi
> >
> > AC_ARG_ENABLE(color,
> > AS_HELP_STRING([--disable-color], [Disable color and syntax
> > highlighting]))
> >
> > +if test "x$enable_nanorc" = xno; then
>
> But... how can one test for 'enable_nanorc' here when it gets set further
> down? True, it works, I've tried, but... how? Does it run through the
> thing twice somehow?
the autoconf core code processes all user flags at the top of the file. so if
the user passed in --enable-nanorc, it'd already be set.
-mike
signature.asc
Description: This is a digitally signed message part.