[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nano-devel] making tiny nano tinier
From: |
Benno Schulenberg |
Subject: |
Re: [Nano-devel] making tiny nano tinier |
Date: |
Thu, 03 Apr 2014 21:17:57 +0200 |
On Thu, Apr 3, 2014, at 16:55, Chris Allegretta wrote:
> On 3/27/14, Benno Schulenberg <address@hidden> wrote:
> > But nowadays, wouldn't it make sense to let --enable-tiny disable
> > *all* features by default, also colour, nanorc and multiple buffers?
> > Which one can then override with selected --enable-something for
> > wanted features?
>
> This was actually the intention all along, and it sounds like what has
> happened is as with most things accidental and not intentional.
Okay, good to know.
Currently there are several occurrences of this:
#if !defined(NANO_TINY) && defined(ENABLE_NANORC)
Should these all be replaced with a simple
#ifdef ENABLE_NANORC
to allow --enable-tiny to be overridden by --enable-nanorc?
(And later on it would then have to change to
#ifndef DISABLE_NANORC
for consistency.)
Benno
--
http://www.fastmail.fm - Faster than the air-speed velocity of an
unladen european swallow