Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] menuconfig / legacy bug
Date: Wed, 13 Nov 2013 09:42:47 +0100	[thread overview]
Message-ID: <87y54s1ym0.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAAXf6LUhpgN16gBY_WFnq=kSepT-LHt-Q3Js-cAHwSUGd2CL6w@mail.gmail.com> (Thomas De Schampheleire's message of "Wed, 13 Nov 2013 09:40:53 +0100")

>>>>> "Thomas" == Thomas De Schampheleire <patrickdepinguin@gmail.com> writes:

Hi,

> I cannot reproduce this problem on my end. I followed the exact steps
> as you described.
> This is on Linux Mint 15, not sure which packages would be relevant
> here. Ncurses is:
> lib32ncurses5-dev: 5.9-10ubuntu4

You need to ensure that you haven't scrolled too far down. The extra
comment lines have to be visible on the screen for the bug to occur.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2013-11-13  8:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-12 21:43 [Buildroot] menuconfig / legacy bug Thomas Petazzoni
2013-11-13  8:40 ` Thomas De Schampheleire
2013-11-13  8:42   ` Peter Korsgaard [this message]
2013-11-13  8:43   ` Yann E. MORIN
2013-11-13  9:05     ` Thomas De Schampheleire
2013-11-13 21:54       ` Yann E. MORIN

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=87y54s1ym0.fsf@dell.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --cc=buildroot@busybox.net \
    /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