From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: did the mapping for the up arrow change?
Date: Wed, 19 May 2004 23:00:27 +0100 [thread overview]
Message-ID: <041ada3ec3c2c72a87ce0dbd2d55dce4@terzarima.net> (raw)
In-Reply-To: <ee9e417a0405191221460fddce@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 78 bytes --]
it's nostalgic. why #include "inode.h" when you can redefine it
each time?
[-- Attachment #2: Type: message/rfc822, Size: 2697 bytes --]
From: Russ Cox <russcox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: did the mapping for the up arrow change?
Date: Wed, 19 May 2004 15:21:49 -0400
Message-ID: <ee9e417a0405191221460fddce@mail.gmail.com>
> Thanks, Recompiling 'vt' solved the problem. (While it didn't with the
> links-port)
The links port has the values hard-coded in plan9.c.
I'm not sure why it doesn't just include keyboard.h instead.
Russ
prev parent reply other threads:[~2004-05-19 22:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-19 18:09 [9fans] " Heiko Dudzus
2004-05-19 18:22 ` Russ Cox
2004-05-19 19:06 ` [9fans] " Heiko Dudzus
2004-05-19 19:21 ` Russ Cox
2004-05-19 22:00 ` Charles Forsyth [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=041ada3ec3c2c72a87ce0dbd2d55dce4@terzarima.net \
--to=forsyth@terzarima.net \
--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).