From: "Tharaneedharan Vilwanathan" <vdharani@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] vmware fusion - plan9 snarf issue
Date: Sun, 28 Dec 2008 04:09:41 -0800 [thread overview]
Message-ID: <dac0a5820812280409w152ed3d9jf1bad54e3630ab03@mail.gmail.com> (raw)
In-Reply-To: <dd6fe68a0812270901l4b8fcbf3u33495721656e3d9f@mail.gmail.com>
hi russ,
okay, this confirms some of the postings in the past.
in my opinion, this shortfall is really a bad one. cut-and-paste is
something very common operation (that too in plan9). it is really
difficult to live without it. i wonder why it has to be this
complicated in vmware.
btw this is what i noticed:
- if i mark(sweep) some text and press middle button in acme or use
send in rio, it works as intended.
- if i mark, cut and paste right there, then also its fine.
- anything else goes for a toss. in fact, the cut and paste buffer
even seems to bring a copy buffer content of previous instance of
guest OS after which i rebooted.
- this issue seems to have shown up in linux OS as well. so plan9 is
probaly yet another platform that got affected.
i am also trying to see if i can keep vmware fusion setup as file
server and avoid using the console (currently snarf buffer issue is
the major issue for me). i am trying to use drwaterm or so to use
plan9. i hope i can resolve my cpu/auth server setup issues.
thanks
dharani
On Sat, Dec 27, 2008 at 9:01 AM, Russ Cox <rsc@swtch.com> wrote:
>> snarf doesnt work properly in plan9 on vmware fusion 2.0 for mac. from what
>> i found this seems to be a known issue. is there any fix available?
>
> no; someone needs to write a new version
> of the vmware tools that works with the latest
> vmware versions.
>
> russ
>
>
next prev parent reply other threads:[~2008-12-28 12:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-25 9:24 Tharaneedharan Vilwanathan
2008-12-27 17:01 ` Russ Cox
2008-12-28 12:09 ` Tharaneedharan Vilwanathan [this message]
2008-12-28 14:44 ` Anthony Sorace
2009-01-02 23:51 ` Tharaneedharan Vilwanathan
2009-01-03 18:21 ` Skip Tavakkolian
2009-01-03 18:57 ` Russ Cox
2009-01-03 21:33 ` Roman V. Shaposhnik
2009-01-03 21:46 ` 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=dac0a5820812280409w152ed3d9jf1bad54e3630ab03@mail.gmail.com \
--to=vdharani@gmail.com \
--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).