9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Paul Lalonde <plalonde@telus.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Acme scrolling tags (was Re:  graphics scaling)
Date: Tue, 23 Dec 2008 10:49:42 -0800	[thread overview]
Message-ID: <5A6D2463-D0B1-42AF-8E23-D7211B00661C@telus.net> (raw)
In-Reply-To: <9d8bfcc919d2e8efdfa2f038071ace90@quanstro.net>

That differs from my experience - I usually run 3 columns on a 30"
monitor, with tags open to two lines for most of my active windows;
the second line typically has an Edit command lying around because you
can't effectively 2-1 chord Edits.  The extra length is also useful
for dealing with the obscenely deep tree our development happens in
(Really, it was easier to fix the editor than to get the rest of the
team to move to a saner tree structure, aggravated by cross-platform/
cross-compile/cross-toolchain requirements that cause a 3 way cross
product of both build and some sources.  If only the world had been
sold on Plan9 in 1993).

I use a mouse with a big click-able scroll wheel (yes, the cheap Dell
ones) that lets me do my button 2 clicks well enough, but also let me
scoll through my windows and tags - I find tag collapse and expansion
really nice with the scroll wheel.

Paul

On 22-Dec-08, at 11:42 AM, erik quanstrom wrote:

>
> On Mon Dec 22 13:57:35 EST 2008, rsc@swtch.com wrote:
>>> not ported.  i'm glad that that hasn't been ported back.
>>> i find multi-line tags annoying 10 times for each time they
>>> are useful.
>>
>> is this an abstract assertion or have you actually tried them?
>>
>> russ
>
> i've used them for quite some time with p9p.  i liked them at
> first, but it didn't wear as well as i thought it would for me.
> tags can be close to the length of the line and cause a second
> line to appear and disappear.  i find that annoying and it
> happens more often than i need a long tag.  esc esc then
> jolts things back the way they were.
>
> - erik
>




  reply	other threads:[~2008-12-23 18:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-22  7:53 [9fans] graphics scaling Tharaneedharan Vilwanathan
2008-12-22  9:23 ` Richard Miller
2008-12-22  9:52   ` cej
2008-12-22 10:34     ` Tharaneedharan Vilwanathan
2008-12-22 11:02       ` Steve Simon
2008-12-22 13:06         ` erik quanstrom
2008-12-22 15:35         ` Brian L. Stuart
2008-12-22 16:37           ` Charles Forsyth
2008-12-22 16:34             ` erik quanstrom
2008-12-22 16:52               ` erik quanstrom
2008-12-22 17:14             ` Brian L. Stuart
2008-12-22 17:58               ` Paul Lalonde
2008-12-22 18:25                 ` Brian L. Stuart
2008-12-22 18:32                   ` erik quanstrom
2008-12-22 18:55                     ` Russ Cox
2008-12-22 19:42                       ` erik quanstrom
2008-12-23 18:49                         ` Paul Lalonde [this message]
2008-12-23 18:54                           ` [9fans] Acme scrolling tags (was Re: graphics scaling) erik quanstrom
2008-12-23 19:18                             ` Paul Lalonde
2008-12-23 19:17                           ` Steve Simon

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=5A6D2463-D0B1-42AF-8E23-D7211B00661C@telus.net \
    --to=plalonde@telus.net \
    --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).