From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] KF|12, etc
Date: Sun, 23 Mar 2014 01:59:13 -0400 [thread overview]
Message-ID: <441fdaaddb7ee377f743626c0052f7cd@brasstown.quanstro.net> (raw)
In-Reply-To: <CAOw7k5htar50oCE+nc_XL8Km2P=wJfLtEdz2UcW3nbv5_ZeNnw@mail.gmail.com>
> I suspect it was meant to describe a new internal sequence of values in the
> 0x1x range, which wasn't thought to be used.
i ment the question in terms of how to we fix it in a coordinated way.
it's not just the f keys, but there are other keys that are common these
days that seem useful.
- erik
next prev parent reply other threads:[~2014-03-23 5:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-22 20:03 erik quanstrom
2014-03-22 21:58 ` cinap_lenrek
2014-03-23 1:01 ` erik quanstrom
2014-03-23 3:09 ` Charles Forsyth
2014-03-23 5:59 ` erik quanstrom [this message]
2014-03-22 22:06 Erik Quanstrom
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=441fdaaddb7ee377f743626c0052f7cd@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).