all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Дилян Палаузов" <dilyan.palauzov@aegee.org>
To: Eli Zaretskii <eliz@gnu.org>, Noam Postavsky <npostavs@gmail.com>
Cc: 35342@debbugs.gnu.org
Subject: bug#35342: configure.ac: scan also libtinfow for tputs()
Date: Sat, 20 Apr 2019 14:51:43 +0000	[thread overview]
Message-ID: <25a5c908243dc4473ba63a167348d1d582bd3771.camel@aegee.org> (raw)
In-Reply-To: <835zr8bw3n.fsf@gnu.org>

Hello,

I altered my ./configure to check tinfow/ncursesw, it uses tputs from tinfow and I have not experienced any problems.

I have forgotten, that I have reported that previously.

Regards
  Дилян

On Sat, 2019-04-20 at 17:16 +0300, Eli Zaretskii wrote:
> > From: Noam Postavsky <npostavs@gmail.com>
> > Date: Sat, 20 Apr 2019 09:44:33 -0400
> > Cc: 35342@debbugs.gnu.org
> > 
> > > on my system I have no libtinfo, libncruses, libcurses, libterminfo and libtermcap.
> > > 
> > > But I have libtinfow and libncursesw, and the former contains tputs.
> > > With emacs 26.2 this is not the case.
> > 
> > Yes, when you reported it previously (Bug#33977), it was only fixed on
> > the master branch (what will become Emacs 27.1).  Should we backport [1:
> > a3d52b3057] to emacs-26 (so it will be fixed in Emacs 26.3)?
> 
> OK, I guess, although I don't really understand whether tputs in
> ncursesw is a drop-in replacement for its namesake in ncurses: we
> don't use wide characters with the curses APIs, AFAIK.






  reply	other threads:[~2019-04-20 14:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-18 16:20 bug#35342: configure.ac: scan also libtinfow for tputs() Дилян Палаузов
2019-04-20 13:44 ` Noam Postavsky
2019-04-20 14:16   ` Eli Zaretskii
2019-04-20 14:51     ` Дилян Палаузов [this message]
2019-04-20 15:31       ` Eli Zaretskii
2019-04-27 17:29     ` Noam Postavsky

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=25a5c908243dc4473ba63a167348d1d582bd3771.camel@aegee.org \
    --to=dilyan.palauzov@aegee.org \
    --cc=35342@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=npostavs@gmail.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.