From: Keith Owens <kaos@ocs.com.au>
To: esr@thyrsus.com
Cc: linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net
Subject: Re: CML2 1.9.6 is available
Date: Wed, 12 Dec 2001 17:32:05 +1100 [thread overview]
Message-ID: <15846.1008138725@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Wed, 12 Dec 2001 00:05:06 CDT." <20011212000506.A5099@thyrsus.com>
On Wed, 12 Dec 2001 00:05:06 -0500,
"Eric S. Raymond" <esr@thyrsus.com> wrote:
>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.
This works for me.
--- cml2-1.9.6/cmlconfigure.py Sun Dec 9 19:27:31 2001
+++ 2.4.16-kbuild-2.5/scripts/cmlconfigure.py Wed Dec 12 17:23:01 2001
@@ -1009,7 +1009,7 @@
def query_popup(self, prompt, initval=None):
"Pop up a window to accept a string."
- maxsymwidth = 30 # Constant
+ maxsymwidth = self.columns - len(prompt) - 2
if initval and len(initval) > maxsymwidth:
self.help_popup("PRESSANY", (lang["TOOLONG"],), beep=1)
return initval
Warning, that is my first bit of Python code (Oh no, now I'm
contaminated too :-).
next prev parent reply other threads:[~2001-12-12 6:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-09 8:32 Eric S. Raymond
2001-12-09 9:04 ` Keith Owens
2001-12-12 5:05 ` Eric S. Raymond
2001-12-12 6:32 ` Keith Owens [this message]
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=15846.1008138725@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=esr@thyrsus.com \
--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
all inboxes | Powered by JetHome®