From: Alexey Dobriyan <adobriyan@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] menuconfig: reclaim 1 more vertical line
Date: Sat, 4 Mar 2023 21:53:14 +0300 [thread overview]
Message-ID: <a5a4bfb5-90ec-447f-82a2-28804e3353b0@p183> (raw)
In-Reply-To: <ae258f1e-5c44-d349-4704-fbf5c7c28b85@infradead.org>
On Sat, Mar 04, 2023 at 09:52:55AM -0800, Randy Dunlap wrote:
> Hi,
>
> On 3/4/23 08:56, Alexey Dobriyan wrote:
> > Empty line after legend is waste, use it for config options.
> >
>
> I don't see an empty line after the legend. For me this patch
> truncates the menu_instructions[] text from 4 lines to 3 lines,
> dropping good/useful help text.
OK, I do need to test this one on more screen sizes.
> menu_instructions[] was already truncated before this patch
> (in an 80x30 size terminal window).
>
> What size terminal are you using?
135 x 31
> > Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
> > ---
> >
> > scripts/kconfig/lxdialog/menubox.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > --- a/scripts/kconfig/lxdialog/menubox.c
> > +++ b/scripts/kconfig/lxdialog/menubox.c
> > @@ -185,7 +185,7 @@ int dialog_menu(const char *title, const char *prompt,
> >
> > height -= 2;
> > width -= 5;
> > - menu_height = height - 10;
> > + menu_height = height - 9;
> >
> > max_choice = MIN(menu_height, item_count());
> >
>
> --
> ~Randy
next prev parent reply other threads:[~2023-03-04 18:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-04 16:55 [PATCH 1/2] menuconfig: delete shadows, reclaim vertical space Alexey Dobriyan
2023-03-04 16:56 ` [PATCH 2/2] menuconfig: reclaim 1 more vertical line Alexey Dobriyan
2023-03-04 17:52 ` Randy Dunlap
2023-03-04 18:53 ` Alexey Dobriyan [this message]
2023-03-04 17:56 ` [PATCH 1/2] menuconfig: delete shadows, reclaim vertical space Randy Dunlap
2023-03-04 18:54 ` Alexey Dobriyan
2023-03-05 6:19 ` Randy Dunlap
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=a5a4bfb5-90ec-447f-82a2-28804e3353b0@p183 \
--to=adobriyan@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=rdunlap@infradead.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