All of lore.kernel.org
 help / color / mirror / Atom feed
From: tobias.jakobi@compleo-cs.com
To: openembedded-core@lists.openembedded.org
Subject: Re: [Kirkstone] joe editor broken with current ncurses
Date: Wed, 22 Nov 2023 02:20:44 -0800	[thread overview]
Message-ID: <31510.1700648444824257996@lists.openembedded.org> (raw)
In-Reply-To: <CANNYZj9g0uu40tyH9+QY-W7s7ND+6OoUOwhDHVxsfF3=1vhikQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 490 bytes --]

I verified this by:
- copying the recipe from master verbatim into our layer
- building our image
- putting image on hardware
- firing up joe

Joe then shows the same broken behaviour that it does with the ncurses 6.3 snapshot in kirkstone.

Or do you want me to replace our kirkstone oe-core layer with master oe-core? I don't think this is going to work anyway, since some of our support layers (we are using a Toradex SoM powered by a NXP i.MX7) are not compatible with master.

[-- Attachment #2: Type: text/html, Size: 522 bytes --]

  reply	other threads:[~2023-11-22 10:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-21 10:23 [Kirkstone] joe editor broken with current ncurses tobias.jakobi
2023-11-21 10:39 ` [OE-core] " Alexander Kanavin
     [not found]   ` <31510.1700646535220677658@lists.openembedded.org>
2023-11-22  9:57     ` Private: " Alexander Kanavin
2023-11-22 10:10   ` tobias.jakobi
2023-11-22 10:12     ` [OE-core] " Alexander Kanavin
2023-11-22 10:20       ` tobias.jakobi [this message]
2023-11-22 10:43         ` Alexander Kanavin
2023-11-22 10:58           ` Tobias Jakobi
2023-11-22 11:12             ` [OE-core] " Alexander Kanavin
2023-11-22 15:20               ` Tobias Jakobi
2023-11-22 15:37                 ` [OE-core] " Richard Purdie
2023-11-22 15:46                   ` Tobias Jakobi
2023-11-22 15:52                     ` [OE-core] " Richard Purdie
2023-11-22 16:27                     ` Alexander Kanavin

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=31510.1700648444824257996@lists.openembedded.org \
    --to=tobias.jakobi@compleo-cs.com \
    --cc=openembedded-core@lists.openembedded.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 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.