public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Eric S. Raymond" <esr@thyrsus.com>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net
Subject: Re: CML2 1.9.6 is available
Date: Wed, 12 Dec 2001 00:05:06 -0500	[thread overview]
Message-ID: <20011212000506.A5099@thyrsus.com> (raw)
In-Reply-To: <20011209033249.A28867@thyrsus.com> <19176.1007888660@ocs3.intra.ocs.com.au>
In-Reply-To: <19176.1007888660@ocs3.intra.ocs.com.au>; from kaos@ocs.com.au on Sun, Dec 09, 2001 at 08:04:20PM +1100

Keith Owens <kaos@ocs.com.au>:
> One niggle, some strings for kuild 2.5 are longer than 30 characters,
> cml2 restricts the string length in make menuconfig.  Only menuconfig
> has this restriction, not oldconfig nor xconfig.  Can the limit be
> removed, or at least changed to $ROWS-n which would adjust to screen
> size?

The only place I see a limit of 30 is in the query_popup function used
for querying for things like search strings, symbol names in the go-to
command, etc. in menuconfig.

The answer is: maybe.  The underlying problem here is that the prompt
string and the string editing area both eat screen width.  30 is about
the largest limit that doesn't blow up the configurator when combined
with the longest prompt strings.
-- 
		<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>

Everything you know is wrong.  But some of it is a useful first approximation.

  reply	other threads:[~2001-12-12  5:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-09  8:32 CML2 1.9.6 is available Eric S. Raymond
2001-12-09  9:04 ` Keith Owens
2001-12-12  5:05   ` Eric S. Raymond [this message]
2001-12-12  6:32     ` Keith Owens
2001-12-12  6:28       ` Eric S. Raymond
2001-12-12 11:45         ` Lars Brinkhoff
2001-12-12 16:04           ` Eric S. Raymond

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=20011212000506.A5099@thyrsus.com \
    --to=esr@thyrsus.com \
    --cc=kaos@ocs.com.au \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.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