From: David Arroyo <david.a.arroyo@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Too big a monitor for Acme?
Date: Fri, 28 Dec 2012 20:39:38 -0500 [thread overview]
Message-ID: <CAF4p8d6C0ew03wcxW9jSvjVHgJbwHhqVH+LBvyxKMTvp2RUiQg@mail.gmail.com> (raw)
In-Reply-To: <8B674272-B9CF-4A43-8AF1-7BB9548680A1@gmail.com>
Acme workflow scales absolutely fantastically to a large monitor. I
would say it is one of Acme's strong points. I recently upgraded to a
27" 2560x1440 display. It's pretty great to have four wide columns
(five if you have a thin one for directory listings) in a single
window. The mouse-warping helps a lot with the increased area. So if
you have some unique setup that doesn't properly move your mouse (like
using Xming on windows to run p9p acme on a remote unix host), you'll
want to get that looked at.
Cheers,
David A.
On Fri, Dec 28, 2012 at 7:25 PM, Matthew Veety <mveety@gmail.com> wrote:
> It works great. More columns the better really.
>
> On Dec 28, 2012, at 19:12, Jacek Masiulaniec <jacekm@dobremiasto.net> wrote:
>
>> I am planning an upgrade of my 24" display. At first I wanted a 30",
>> but am now having some doubts regarding acme experience on these
>> larger displays.
>>
>> Did you notice significant mousing overhead, owing to the area increase?
>>
>> Were speed/acceleration tweaks sufficient to mask it?
>>
>> Any report is welcome, as I have no test system.
>>
>> Thanks.
>>
>> Jacek
>>
>
next prev parent reply other threads:[~2012-12-29 1:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-29 0:12 Jacek Masiulaniec
2012-12-29 0:25 ` Matthew Veety
2012-12-29 1:39 ` David Arroyo [this message]
2012-12-31 11:32 ` Peter A. Cejchan
2012-12-31 18:21 ` David Arroyo
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=CAF4p8d6C0ew03wcxW9jSvjVHgJbwHhqVH+LBvyxKMTvp2RUiQg@mail.gmail.com \
--to=david.a.arroyo@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).