From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] links bugfix
Date: Sun, 13 Jun 2004 21:43:11 -0600 [thread overview]
Message-ID: <44559137aff5d4eb017a4760b09119a2@plan9.ucalgary.ca> (raw)
In-Reply-To: <36a665624cf5daceae8863202c979c43@granite.cias.osakafu-u.ac.jp>
>> note that this is the fixed font version. the varfont one is just too
>> messy to fix.
>
> Does this mean it cannot be compiled in the new sources environment?
> I haven't checked this yet, but I was able to compile it on a older source
> trees of Fossil server, but failed on a newer en's file server source. I haven't
> checked what is the difference between two, because I had been having Fossil
> server for a long time not used heavily...☺
>
> Kenji
it should be as simple as changing:
case 0x80:
*k = KBD_DOWN;
break;
/* within Unicode private-use space */
into:
/* within Unicode private-use space */
case 0xf800:
*k = KBD_DOWN;
break;
in 'plan9_translate_key()' in plan9.c...
andrey
prev parent reply other threads:[~2004-06-14 3:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-11 15:36 andrey mirtchovski
2004-06-14 1:34 ` Kenji Okamoto
2004-06-14 3:43 ` andrey mirtchovski [this message]
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=44559137aff5d4eb017a4760b09119a2@plan9.ucalgary.ca \
--to=mirtchov@cpsc.ucalgary.ca \
--cc=9fans@cse.psu.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).