From: Anton Altaparmakov <aia21@cam.ac.uk>
To: esr@thyrsus.com
Cc: linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net
Subject: CML2 1.1.5, more comments
Date: Wed, 18 Apr 2001 02:12:00 +0100 [thread overview]
Message-ID: <5.0.2.1.2.20010418020921.03e99d40@pop.cus.cam.ac.uk> (raw)
In-Reply-To: <20010417174407.A6667@thyrsus.com>
Hi,
A few comments on cml2 1.1.5 running on my Pentium 133S (make menuconfig,
fastmode):
- Instantaneous moving up/down! Excellent!
- Thanks for dark blue! The cyan was barely readable. Now all the colours
are nicely readable. I don't necessarily like your choice of colours but as
long as I can read the text, that's fine.
- When I set something to yes it goes green. When I then set something else
to yes the new one goes green, too, but the old one also remains green. Is
this intended? (i.e. does green mean "already visited" or something like
that?) Also, on the CPU selection menu, it started off with two of the CPUs
already in green (but only one with a yes). Is that a feature or a bug?
- Moving left/right can still be quite painfully slow...
- Setting options is sometimes very slow, sometimes ok... (depends on
complexity of underlying rules I guess)
It is definitely usable now compared to 1.1.0. But if the last two points
could be speeded up, it would be great.
Best regards,
Anton
--
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Linux NTFS Maintainer / WWW: http://sourceforge.net/projects/linux-ntfs/
ICQ: 8561279 / WWW: http://www-stu.christs.cam.ac.uk/~aia21/
next prev parent reply other threads:[~2001-04-18 1:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-17 21:44 CML2 1.1.6, aka "I think I should have stayed in bed this morning." Eric S. Raymond
2001-04-18 1:12 ` Anton Altaparmakov [this message]
2001-04-18 13:58 ` CML2 1.1.5, more comments 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=5.0.2.1.2.20010418020921.03e99d40@pop.cus.cam.ac.uk \
--to=aia21@cam.ac.uk \
--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®