From: steve@cegelecproj.co.uk (Steve_Kilbane)
To: sam-fans@hawkwind.utcs.toronto.edu
Subject: menu line characters
Date: Tue, 10 May 1994 07:23:05 -0400 [thread overview]
Message-ID: <9405101023.AA04203@zombie.gec-epl.co.uk> (raw)
minor gripe: the menu lines use '+' and '*' to indicate the number of windows
open on a file. wouldn't it make more sense to use characters that don't have
special meanings within a regular expression? that would save on escaping
these characters on the odd occasion they're used in a command. The following
are available (I think): ! # % : ; " < > ~
Although it's a pretty arbitrary decision about which should be used ('-+*'
makes some sense, since each character has more used pixels than the previous
one), '-:;' '-%#' and '-<>' make a small amount of sense to me....
steve
reply other threads:[~1994-05-10 11:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9405101023.AA04203@zombie.gec-epl.co.uk \
--to=steve@cegelecproj.co.uk \
--cc=sam-fans@hawkwind.utcs.toronto.edu \
/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;
as well as URLs for NNTP newsgroup(s).