From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] last update got strange acme behaviour
Date: Thu, 25 Jul 2002 16:42:38 +0900 [thread overview]
Message-ID: <976604dd42baa1aa2000207474bb8aef@granite.cias.osakafu-u.ac.jp> (raw)
[-- Attachment #1: Type: text/plain, Size: 608 bytes --]
I searched once more the reason of this. There is a two version of
acme win program, one works fine, and the other does not.
The first is that one before I fetched many patches and recompiled;
ls -l /n/dump/2002/0723/acme/bin/386/win
--rwxrwxr-x M 9 sys sys 174975 Apr 2 01:42 /n/dump/2002/0723/acme/bin/386/win
and the second is that after I recomplied:
ls -l /acme/bin/386/win
--rwxrwxr-x M 9 sys sys 175343 Jul 24 16:48 /acme/bin/386/win
As there is no difference between these sources, I suppose this reflect the
difference between the lower libraries, probably libc (?).
Kenji
[-- Attachment #2: Type: message/rfc822, Size: 2171 bytes --]
From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: [9fans] last update got strange acme behaviour
Date: Thu, 25 Jul 2002 10:47:55 +0900
Message-ID: <9ddb596b212ad3a7fea4d865385f5429@granite.cias.osakafu-u.ac.jp>
I got last update (July 24) from plan9 sources using replica/pull.
I recompiled all the things by the new source trees after that pull.
Now I have a strange behaviour of win command in acme.
In an acme window,
'win rc' command runs smoothly, and makes another acme window
with the prompt of
term%
Then, I dispatched the command ls at the window, and got error as
rc: note: '0x0e'
'0x0e' means so control code.
I'd be glad if someone could give me where I should search the problem.
Kenji
next reply other threads:[~2002-07-25 7:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-25 7:42 okamoto [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-25 1:47 okamoto
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=976604dd42baa1aa2000207474bb8aef@granite.cias.osakafu-u.ac.jp \
--to=okamoto@granite.cias.osakafu-u.ac.jp \
--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).