public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Terminfo bug in screen-256color
Date: Tue, 20 Oct 2015 21:02:00 -0000	[thread overview]
Message-ID: <1445374958.12108.56.camel@cygwin.com> (raw)
In-Reply-To: <87si55nz07.fsf@Rainer.invalid>

On Tue, 2015-10-20 at 21:03 +0200, Achim Gratz wrote:
> Achim Gratz writes:
> >> Can you confirm that this patch contains the necessary changes:
> >>
> >> http://pkgs.fedoraproject.org/cgit/ncurses.git/tree/ncurses-kbs.patch
> >
> > The solution I used was different IIRC, but I'll have to dig out the
> > details.
> 
> I don't know much about these things, but it seems that the patch you're
> linking to deals with the interpretation of the backspace key in certain
> situations?

You are correct, that patch is unrelated.  However, it turns out that
ncurses-6.0 ships with new 'tmux' and 'tmux-256color' terminfos, which
appear to include the settings indicated in said FAQ.  tmux should use
these instead of the screen terminfos.

I'm in the process of triple-checking that I have the correct options to
avoid ABI breakage in ncurses-6.0, at which point I'll upload and you
can use these instead.

--
Yaakov



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2015-10-20 21:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-20  7:16 Achim Gratz
2015-10-20 17:19 ` Yaakov Selkowitz
2015-10-20 18:53   ` Achim Gratz
2015-10-20 19:03     ` Achim Gratz
2015-10-20 21:02       ` Yaakov Selkowitz [this message]

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=1445374958.12108.56.camel@cygwin.com \
    --to=yselkowitz@cygwin.com \
    --cc=cygwin@cygwin.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).