git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonas Fonseca <fonseca@diku.dk>
To: git@vger.kernel.org
Subject: Re: [ANNOUNCE] tig-0.13
Date: Thu, 15 Jan 2009 14:06:59 +0100	[thread overview]
Message-ID: <20090115130659.GA18081@diku.dk> (raw)
In-Reply-To: <20090115014617.GC6937@b2j>

bill lam <cbill.lam@gmail.com> wrote Thu, Jan 15, 2009:
> On Thu, 15 Jan 2009, Jonas Fonseca wrote:
> > Yes, it works. You can either create a file called config.make with a
> > line saying:
> > 
> > 	LDLIBS = -lncursesw
> > 
> > or use the configure file. If you are not using the tarball generate it
> > with:
> > 
> > 	make configure
> 
> I use the git source. Even after make configure and  ./configure, it
> still links to the non-unicode ncurses.

I haven't tested the configure script on a lot of system, so it might be
a bit debian/ubuntu/gentoo centered in that use of ncursesw requires the
presence of a {/usr/incude/}ncursesw/ncurses.h header. Where are the
unicode ncurses.h files found on your system?

> Should it make ncursesw as 
> default if detected available albeit this can be changed manually?

I would prefer that the "default" (running make without configure) has
as few dependencies as possible. Since the unicode version of ncurses is
probably more rare than the non-unicode version it is probably a bad
idea to use ncursesw by default. However, if you use the configure
script ncursesw is the default, when it is available.

-- 
Jonas Fonseca

  reply	other threads:[~2009-01-15 13:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-13 23:36 [ANNOUNCE] tig-0.13 Jonas Fonseca
2009-01-14 16:33 ` Ted Pavlic
2009-01-14 23:24 ` bill lam
2009-01-14 23:56   ` Jonas Fonseca
2009-01-15  1:46     ` bill lam
2009-01-15 13:06       ` Jonas Fonseca [this message]
2009-01-15 14:50         ` bill lam
2009-01-15 15:05           ` Adeodato Simó
2009-01-15 15:08           ` Jonas Fonseca
2009-01-15 15:41             ` bill lam

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090115130659.GA18081@diku.dk \
    --to=fonseca@diku.dk \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).