9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Federico G. Benavento" <benavento@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] vmware fusion 3.0.1 and VESA
Date: Sat, 30 Jan 2010 05:11:19 -0200	[thread overview]
Message-ID: <32d987d51001292311m3806261bh8e4c8314578e0276@mail.gmail.com> (raw)
In-Reply-To: <467ac3901001292113i5e0c50bek9d3517c3e5871993@mail.gmail.com>

> Also, does the mouse one-three combination work in acme?
>
>

they do, but I found it's quite better to have a standalone cpu server
in vmware and drawterm from the host, it makes your life easier,
being able to access the local drives in /mnt/term/ and to share the
snarf buffer.

others like tim run vmware fullscreen, so I'll let them to comment on
that


--
Federico G. Benavento



  reply	other threads:[~2010-01-30  7:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-30  5:13 kazumi iwane
2010-01-30  7:11 ` Federico G. Benavento [this message]
2010-01-30 20:23 ` Tim Newsham

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=32d987d51001292311m3806261bh8e4c8314578e0276@mail.gmail.com \
    --to=benavento@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).