[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Nano-devel] can't build without curses/ncurses and a string change

From: Chris Allegretta
Subject: Re: [Nano-devel] can't build without curses/ncurses and a string change suggestion
Date: Tue, 3 Mar 2015 10:52:22 -0500

On 3/2/15, Benno Schulenberg <address@hidden> wrote:
> Hello Marco,
> On Mon, Mar 2, 2015, at 13:52, Marco Colombo wrote:
>> configure: WARNING:
>> *** No curses lib available.  Consider getting the official ncurses
>> *** distribution from if you get
>> *** errors compiling nano.
>> [...]
>> so it seems that the lack of curses/ncurses shouldn't be a problem.
> Not really.  I read the above warning as: you will likely have problems
> compiling nano without ncurses.  But it might not be a problem if you
> have something else that can replace ncurses, like slang.
>> so, either configure should stop with an error, or the compilation
>> should be successful even without curses/ncurses.
> I agree that ./configure should detect whether enough stuff is
> present to successfully compile nano.  But I don't know how to
> do that.

Sure, we can fix that in 2.5.

>> also, I think that the following string (I believe it's very recent)
>> "the many translators and the TP" would be more intelligible if it read
>> "the many translators and the Translation Project".
> True.  But it is a very hidden phrase, and there is no harm in
> being a little puzzling there.  And I wanted to prevent translators
> translating the words "Translation Project".

Maybe we could put the URL of the TP on the next line?  But in general
I agree, it's fine as-is.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]