From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] broken acme
Date: Thu, 20 Feb 2003 09:44:43 -0500 [thread overview]
Message-ID: <0a9a3ca811fbf5955bf19f0dea746255@plan9.bell-labs.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0302201509220.28739-100000@diogenis.ceid.upatras.gr>
I'm running VMware 3.2 (build 2230) right now
on Windows XP, and have no problems with the
snarf buffer. I used Windows 2000 for a while
also with no problems.
Perhaps you are running some other Windows program
that is doing weird things with the snarf buffer?
Does copy and paste work in, say, notepad?
Another thing to try would be to copy something
in Windows and then cat /dev/snarf in Plan 9.
I think this might be a VMware bug rather than a Plan 9 bug.
Russ
next prev parent reply other threads:[~2003-02-20 14:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 13:19 Anastasopoulos S
2003-02-20 14:44 ` Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-19 12:27 Anastasopoulos S
2003-02-19 13:49 ` Russ Cox
2003-02-19 14:01 ` Anastasopoulos S
2003-02-19 14:17 ` Russ Cox
2003-02-19 16:18 ` Jack Johnson
2003-02-19 16:58 ` Russ Cox
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=0a9a3ca811fbf5955bf19f0dea746255@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--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).